Segfault `SIGSEGV (Address boundary error)` when running examples on main about bevy

[JMS55]

Can you run it through GDB and see where it crashes?

[RobWalt]

Can you run it through GDB and see where it crashes?

I'm not too familiar with GDB. Can you give me some instructions on what to do exactly?

[JMS55]

1. Compile an example that doesn't use any assets, e.g. 3d_scene (or set BEVY_ASSET_ROOT if needed)
2. gdb target/debug/examples/foo
3. r

[Friz64]

What happens when you disable AMDVLK (so the Mesa Vulkan (RADV) drivers are used)?

[RobWalt]

1. Compile an example that doesn't use any assets, e.g. 3d_scene (or set BEVY_ASSET_ROOT if needed)

   2. gdb target/debug/examples/foo

   3. r

Ahh, ok sorry. I thought you had some specific breakpoints in mind. Here's the gdb output

(gdb) r
Starting program: /home/aviac/repos/github/RobWalt/bevy/target/debug/examples/clear_color
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/nix/store/apab5i73dqa09wx0q27b6fbhd1r18ihl-glibc-2.39-31/lib/libthread_db.so.1".
[New Thread 0x7ffff7b366c0 (LWP 372130)]
[New Thread 0x7ffff79356c0 (LWP 372131)]
[New Thread 0x7ffff77316c0 (LWP 372132)]
[New Thread 0x7ffff752d6c0 (LWP 372133)]
[New Thread 0x7ffff73296c0 (LWP 372134)]
[New Thread 0x7ffff71256c0 (LWP 372135)]
[New Thread 0x7ffff6f216c0 (LWP 372136)]
[New Thread 0x7ffff6d1d6c0 (LWP 372137)]
[New Thread 0x7ffff6b166c0 (LWP 372138)]
[New Thread 0x7ffff69156c0 (LWP 372139)]
[New Thread 0x7ffff67116c0 (LWP 372140)]
[New Thread 0x7ffff650d6c0 (LWP 372141)]
[New Thread 0x7ffff63096c0 (LWP 372142)]
[New Thread 0x7ffff61056c0 (LWP 372143)]
[New Thread 0x7ffff5f016c0 (LWP 372144)]
[New Thread 0x7ffff5cfd6c0 (LWP 372145)]
[New Thread 0x7ffff5af96c0 (LWP 372146)]
[New Thread 0x7ffff58f56c0 (LWP 372147)]
[New Thread 0x7ffff56f16c0 (LWP 372148)]
[New Thread 0x7ffff54ed6c0 (LWP 372149)]
[New Thread 0x7ffff52e96c0 (LWP 372150)]
[New Thread 0x7ffff50e26c0 (LWP 372151)]
[New Thread 0x7ffff4ee16c0 (LWP 372152)]
[New Thread 0x7ffff4cdd6c0 (LWP 372153)]
[New Thread 0x7ffff4ad66c0 (LWP 372154)]
[New Thread 0x7ffff48d26c0 (LWP 372155)]
[New Thread 0x7ffff46d16c0 (LWP 372156)]
[New Thread 0x7ffff44ca6c0 (LWP 372157)]
[New Thread 0x7ffff42c96c0 (LWP 372158)]
[New Thread 0x7fff87fff6c0 (LWP 372159)]
[New Thread 0x7fff87dfe6c0 (LWP 372160)]
[New Thread 0x7fff87bfd6c0 (LWP 372161)]
2024-05-25T07:48:34.834429Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 24.05 NixOS", kernel: "6.6.31", cpu: "AMD Ryzen 9 7950X3D 16-Core Processor", core_count: "16", memory: "61.9 GiB" }
2024-05-25T07:48:34.840251Z  INFO bevy_winit::system: Creating new window "App" (Entity { index: 0, generation: 1 })
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /nix/store/qdfdv7axm2zxj19k43g9j68qgcphdraz-mesa-24.0.6-drivers/lib/libvulkan_nouveau.so.
Use `info auto-load python-scripts [REGEXP]' to list them.
[Detaching after vfork from child process 372162]
[Detaching after vfork from child process 372163]
[Detaching after vfork from child process 372164]
[New Thread 0x7fff713fb6c0 (LWP 372167)]
[New Thread 0x7fff70bfa6c0 (LWP 372168)]
2024-05-25T07:48:35.213692Z  INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 6600", vendor: 4098, device: 29695, device_type: DiscreteGpu, driver: "AMD open-source driver", driver_info: "2023.Q4.2 (LLPC)", backend: Vulkan }
[Detaching after vfork from child process 372169]
[New Thread 0x7fff56fff6c0 (LWP 372170)]
[New Thread 0x7fff567fe6c0 (LWP 372171)]
[New Thread 0x7fff55ffd6c0 (LWP 372172)]
[New Thread 0x7fff5577a6c0 (LWP 372175)]
2024-05-25T07:48:35.548877Z  INFO gilrs_core::platform::platform::gamepad: Gamepad /dev/input/event1 (ASRock LED Controller) connected.
[New Thread 0x7fff555796c0 (LWP 372176)]
[New Thread 0x7fff553786c0 (LWP 372177)]
[New Thread 0x7fff549776c0 (LWP 372178)]
2024-05-25T07:48:35.624592Z  INFO bevy_input::gamepad: Gamepad { id: 0 } Connected

Thread 8 "Async Compute T" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6f216c0 (LWP 372136)]
0x00007fff6149fdcd in ?? () from /nix/store/b35zqnyfcknmaa0q7hfdfffnxrw2d2z7-amdvlk-2023.Q4.2/lib/amdvlk64.so

Here's also the lldb output

(lldb) r
Process 380466 launched: '/home/aviac/repos/github/RobWalt/bevy/target/debug/examples/clear_color' (x86_64)
2024-05-25T07:51:40.590588Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 24.05 NixOS", kernel: "6.6.31", cpu: "AMD Ryzen 9 7950X3D 16-Core Processor", core_count: "16", memory: "61.9 GiB" }
2024-05-25T07:51:40.598919Z  INFO bevy_winit::system: Creating new window "App" (Entity { index: 0, generation: 1 })
Process 380466 stopped and restarted: thread 1 received signal: SIGCHLD
Process 380466 stopped and restarted: thread 1 received signal: SIGCHLD
Process 380466 stopped and restarted: thread 1 received signal: SIGCHLD
2024-05-25T07:51:41.023016Z  INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 6600", vendor: 4098, device: 29695, device_type: DiscreteGpu, driver: "AMD open-source driver", driver_info: "2023.Q4.2 (LLPC)", backend: Vulkan }
Process 380466 stopped and restarted: thread 1 received signal: SIGCHLD
2024-05-25T07:51:41.307041Z  INFO gilrs_core::platform::platform::gamepad: Gamepad /dev/input/event1 (ASRock LED Controller) connected.
2024-05-25T07:51:41.382348Z  INFO bevy_input::gamepad: Gamepad { id: 0 } Connected
Process 380466 stopped
* thread #7, name = 'Async Compute T', stop reason = signal SIGSEGV: address not mapped to object (fault address: 0x8)
    frame #0: 0x00007fff6149fdcd amdvlk64.so`___lldb_unnamed_symbol50394 + 29
amdvlk64.so`___lldb_unnamed_symbol50394:
->  0x7fff6149fdcd <+29>: movzbl 0x8(%rsi), %esi
    0x7fff6149fdd1 <+33>: movslq (%rdx,%rsi,4), %rax
    0x7fff6149fdd5 <+37>: addq   %rdx, %rax
    0x7fff6149fdd8 <+40>: jmpq   *%rax

What happens when you disable AMDVLK (so the Mesa Vulkan (RADV) drivers are used)?

Yeah I was also considering the driver to be the issue. Especially since I recently update to a newer version. But a rollback to the previous version also didn't fix it yet. I'll try out your suggestion! ... Yeah that seems to work for me. Thanks for the idea!

Not so sure what the learnings are from this issue here. I guess I have to wait until it's fixed in the amdvlk drivers.

Sorry for the trouble right before the release. I'm closing this.

[RobWalt]

More details for anyone else stumbling over this issue:

• After the update I was on version 2023.Q4.2 of the amdvlk driver and I thought that was the issue
• It seems to persist after downgrading to 2023.Q4.1