This is on 19.0.0-rc2 compiled with --buildtype=debug, but debug symbols are still missing? I'm not sure why that is the case.

Are you sure you use dynamic bindings correctly first?
Can you share a link to your custom app?

I'm not sure what you mean, I don't use any of the *_DYNAMIC variants of DescriptorType.

This is how I define the layout of 2nd Descriptor Set I'm trying to bind in the failing call:
https://github.com/farnoy/renderer/blob/3d42799a1fa6f6881c86506d9f76670899f0f7a9/src/forward_renderer/renderer.rs#L113-L142

And this is how I bind it:
https://github.com/farnoy/renderer/blob/3d42799a1fa6f6881c86506d9f76670899f0f7a9/src/forward_renderer/renderer.rs#L703-L710

If I try binding just the 2nd one, it does not crash and lets me submit that command buffer to the compute queue. The problem must be with the first set (called mvp_set in my app). It fails to bind in a graphics context as well. I will keep fiddling to see if I can change the definition until it binds successfully.

Its (failing) layout is:

    vk::DescriptorSetLayoutBinding {
            binding: 0,
            descriptor_type: vk::DescriptorType::UNIFORM_BUFFER,
            descriptor_count: 1,
            stage_flags: vk::ShaderStageFlags::VERTEX | vk::ShaderStageFlags::COMPUTE,
            p_immutable_samplers: ptr::null(),
    }

So I've duplicated the binding of that set into two separate bindings, one for VERTEX stage, one for COMPUTE. And I updated them the same way:

Thread 0, Frame 0:
vkUpdateDescriptorSets(device, descriptorWriteCount, pDescriptorWrites, descriptorCopyCount, pDescriptorCopies) returns void:
    device:                         VkDevice = 0x5577e9626f10
    descriptorWriteCount:           uint32_t = 2
    pDescriptorWrites:              const VkWriteDescriptorSet* = 0x7ffdeda2aee0
        pDescriptorWrites[0]:           const VkWriteDescriptorSet = 0x7ffdeda2aee0:
            sType:                          VkStructureType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET (35)
            pNext:                          const void* = NULL
            dstSet:                         VkDescriptorSet = 0x5577e9626c00
            dstBinding:                     uint32_t = 0
            dstArrayElement:                uint32_t = 0
            descriptorCount:                uint32_t = 1
            descriptorType:                 VkDescriptorType = VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER (6)
            pImageInfo:                     const VkDescriptorImageInfo* = UNUSED
            pBufferInfo:                    const VkDescriptorBufferInfo* = 0x7ffdeda2ad80
                pBufferInfo[0]:                 const VkDescriptorBufferInfo = 0x7ffdeda2ad80:
                    buffer:                         VkBuffer = 0x5577e9626b10
                    offset:                         VkDeviceSize = 0
                    range:                          VkDeviceSize = 262144
            pTexelBufferView:               const VkBufferView* = UNUSED
        pDescriptorWrites[1]:           const VkWriteDescriptorSet = 0x7ffdeda2af20:
            sType:                          VkStructureType = VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET (35)
            pNext:                          const void* = NULL
            dstSet:                         VkDescriptorSet = 0x5577e9626c00
            dstBinding:                     uint32_t = 1
            dstArrayElement:                uint32_t = 0
            descriptorCount:                uint32_t = 1
            descriptorType:                 VkDescriptorType = VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER (6)
            pImageInfo:                     const VkDescriptorImageInfo* = UNUSED
            pBufferInfo:                    const VkDescriptorBufferInfo* = 0x7ffdeda2ad80
                pBufferInfo[0]:                 const VkDescriptorBufferInfo = 0x7ffdeda2ad80:
                    buffer:                         VkBuffer = 0x5577e9626b10
                    offset:                         VkDeviceSize = 0
                    range:                          VkDeviceSize = 262144
            pTexelBufferView:               const VkBufferView* = UNUSED
    descriptorCopyCount:            uint32_t = 0
    pDescriptorCopies:              const VkCopyDescriptorSet* = 0x5577e82ee320

Now I get a different assertion error, but only when using the api_dump layer (without other validation errors):

v4: ../mesa-19.0.0-rc2/src/amd/vulkan/radv_cmd_buffer.c:2727: radv_bind_descriptor_set: Assertion `!(set->layout->flags & VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR)' failed.

This really confuses me, because I am not using or enabling the push descriptor extension, how could this bit be set?

I've made some unrelated changes (the mvp_set and its layout is still the same), and even started using advanced descriptor indexing features with partially bound descriptor sets and suddenly it's working. Not with validation layers though, that still segfaults when recording commands.

If you explain me how to build your own app, I should be able to reproduce the problem myself and investigate.

Alright, so here goes:

# glTF-Sample-Models submodule is pretty big
$ git clone --recurse-submodules https://github.com/farnoy/renderer.git

Install rustup from https://rustup.rs, linux distros usually package their own. Then you night a nightly version of the Rust compiler:

$ rustup install nightly

Then from the cloned repo:

# to get the version that uses descriptor indexing and partially bound sets:
$ git checkout a8be0be1c44cac83e1f24fc066a97ee7b82be516
$ rustup run nightly cargo run --release
# this should work and render some helmets and a ground mesh
# WSAD and mouse gets you around
$ rustup run nightly cargo run --release --features validation
# this enables lunarg validation layers which for me produce a SEGFAULT

# to get the old version of my app from the initial report:

$ git checkout 3d42799a1fa6f6881c86506d9f76670899f0f7a9
$ rustup run nightly cargo run --release --features validation
# On on vulkan ICD loader 1.1.96, these caused the weird dynamicOffset assertions in radv,
# on loader 1.1.99, these hang my GPU and I need to reset my machine

Let me know if you have any questions, I also upgraded the kernel from 4.20.6 to 4.20.7 since the original report, but I think it's more likely the vulkan loader upgrade changed behavior of my program in version 3d42799a1fa6f6881c86506d9f76670899f0f7a9.

Do you still have a problem with binding offsets?

Nope, I made some unrelated changes and I'm not hitting this problem anymore.

I assume it was a bug on your side?

I don't think so, like I said I wasn't using dynamic offsets at all, maybe validation layers added something but I'm not sure anymore.