-
Notifications
You must be signed in to change notification settings - Fork 272
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
Test layer triggers crash if enabled #102
Comments
I'm not sure this is really a problem. We never intended to distribute the test layer. It's only real purpose is to create a layer that we can enable/disable as part of the loader tests. As a result, we never bother getting far enough to create a device with that layer. Is there any reason you want to be enabling the layer? I don't think it does anything useful. |
I’m trying to figure out my rendercmd crash and so far all the layers I’ve tried are crashing:
|
Your stack trace looks like you're not actually entering the enabled layer. It looks to me like the loader's dispatch table has a null pointer for the function in question. This could mean that there's a loader bug or the layers are returning their function pointers wrong. My advice would be to see if validation layers work. Those should be doing all of the initialization behavior correct, so if even those crash we either have a bug or something wrong with your system's configuration. |
We haven't progressed this in quite a while and it still sounds to me like there's no error here because the layer was never meant to be used outside of the tests. As such, I'm closing this. |
I've tried this with a couple of application :
VK_INSTANCE_LAYERS=VK_LAYER_LUNARG_test COGL_DRIVER=vulkan gdb --args ../cogl/examples/cogl-hello
Same with gfxbench :
VK_INSTANCE_LAYERS=VK_LAYER_LUNARG_test gdb --args ./bin/testfw_app -t vulkan_5_normal --gfx=xcb_vulkan -w1280 -h720
The text was updated successfully, but these errors were encountered: