-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vkconfig: segfaults while handling segfault, forever #2167
Comments
The contents of the written vkconfig.conf:
|
gdb with a release build:
Running a debug build:
There are two problems here. One is that we're indeed segfaulting continuously, getting stuck in a loop of segfault -> surrender config -> segfault -> .... The other problem is that on the path shown in the backtrace, CreateInstance assumes that the vulkan shared library has been loaded successfully, but UpdateDevices doesn't actually ensure this. The only thing keeping us from calling a null function pointer is the debug-only |
Hi, Do you have an installed Vulkan Loader and driver? |
In the context of this bug, no. The In this call stack,
nobody checks that QLibrary::load succeeds. CreateInstance resolves The segfault leads to a second bug, where vkconfig ends up doing |
You are correct that Vulkan Loader not being installed was not handle correctly in Vulkan Configurator 2. I could reproduce the crash.
|
With
Vulkan Configurator version 2.6.2
installed on NixOS, when runningvkconfig
(orvkconfig gui
), vkconfig produces no output on stderr or stdout, and no GUI appears. The process doesn't respond to SIGINT. Attaching strace to the process shows that it is repeatedly recreating the configuration in~/.config/LunarG/vkconfig.conf
, seemingly in an infinite loop.The following should be one full repeating segment (but it might span two iterations, i.e. the segment might not be aligned with the iteration boundary). Just in case, here's the full trace as well:
strace.tar.gz
The text was updated successfully, but these errors were encountered: