search

andrewrk / zig-window

window client library
117 stars 13 forks source link

Fails on Manjaro with Nvidia GPU #9

Open creikey opened 3 years ago

creikey commented 3 years ago 
➜  Downloads ./static-window8         
debug: detecting whether we are running in the dynamic linker
debug: we're not. detecting the dynamic linker path
debug: prepare to execve reload
debug: dyld_path=/lib64/ld-linux-x86-64.so.2
debug: setting environment variable 'LD_PRELOAD=libdl.so.2'
debug: detecting whether we are running in the dynamic linker
debug: got dlopen. detect libc
debug: initialize vulkan
debug: vulkan initialized, dlopening xcb
debug: connecting to X11
debug: opening window
error: VulkanInitializationFailed
???:?:?: 0x235625 in ??? (???)
???:?:?: 0x26770d in ??? (???)
???:?:?: 0x276eca in ??? (???)
???:?:?: 0x2784e9 in ??? (???)
???:?:?: 0x26d7a9 in ??? (???)
???:?:?: 0x2665a3 in ??? (???)
???:?:?: 0x25d7f1 in ??? (???)
andrewrk commented 3 years ago

(1) can you confirm vkcube works on the same machine? (2) try the latest patch: https://andrewkelley.me/temp/static-window9

creikey commented 3 years ago

@andrewrk I just compiled vkcube and ran it and it seems to work, screenshot: image

That latest patch has the same error:

➜  Downloads ./static-window9
debug: detecting whether we are running in the dynamic linker
debug: we're not. detecting the dynamic linker path
debug: prepare to execve reload
debug: dyld_path=/lib64/ld-linux-x86-64.so.2
debug: setting environment variable 'LD_PRELOAD=libdl.so.2 libpthread.so.0'
debug: detecting whether we are running in the dynamic linker
debug: got dlopen. detect libc
debug: initialize vulkan
debug: vulkan initialized, dlopening xcb
debug: connecting to X11
debug: opening window
error: VulkanInitializationFailed
???:?:?: 0x235645 in ??? (???)
???:?:?: 0x2676cd in ??? (???)
???:?:?: 0x2770aa in ??? (???)
???:?:?: 0x2786c9 in ??? (???)
???:?:?: 0x26dbe9 in ??? (???)
???:?:?: 0x266563 in ??? (???)
???:?:?: 0x25d961 in ??? (???)
creikey commented 3 years ago

Also just tested with the binary provided by the prebuilt vulkan-tools package and it works

andrewrk commented 3 years ago

Thanks for the follow-up! Looks like you have found the next system on the hit list :slightly_smiling_face:

creikey commented 3 years ago

@andrewrk I have the project compiled from scratch with zig master, is there any way to view the stack trace from the vulkan call? as in where checkSuccess was called from

andrewrk commented 3 years ago

Yes - the trick is to use the file command of gdb: 

(gdb) file ./zig-cache/bin/static-window
creikey commented 3 years ago 
(gdb) file ./zig-cache/bin/static-window 
Reading symbols from ./zig-cache/bin/static-window...
(gdb) run
Starting program: /home/creikey/Documents/projects/zig-window/zig-cache/bin/static-window 
debug: detecting whether we are running in the dynamic linker
debug: we're not. detecting the dynamic linker path
debug: prepare to execve reload
debug: dyld_path=/lib64/ld-linux-x86-64.so.2
debug: setting environment variable 'LD_PRELOAD=libdl.so.2 libpthread.so.0'
process 101570 is executing new program: /usr/lib/ld-2.32.so
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
debug: detecting whether we are running in the dynamic linker
debug: got dlopen. detect libc
debug: initialize vulkan
debug: vulkan initialized, dlopening xcb
debug: connecting to X11
debug: opening window
error: VulkanInitializationFailed
???:?:?: 0x235674 in ??? (???)
???:?:?: 0x2676cd in ??? (???)
???:?:?: 0x27711a in ??? (???)
???:?:?: 0x278739 in ??? (???)
???:?:?: 0x26dc49 in ??? (???)
???:?:?: 0x266553 in ??? (???)
???:?:?: 0x25d961 in ??? (???)
[Inferior 1 (process 101570) exited with code 01]
(gdb)

It seems as if there is still no stacktrace

andrewrk commented 3 years ago

You gotta do the file command after the execve happens (at the end). And then do bt in gdb.