Recent searches
Search options
Let's close out the year with a driver debugging war story: http://nhaehnle.blogspot.com/2023/12/vulkan-driver-debugging-stories.html
@nh Oof, yeah. Debugging under Wine/Proton can definitely be a real pain. I have to resort to attaching after-the-fact as well, but in order to make gdb aware of how the .so files are loaded, it's actually sufficient to simply invoke "gdb -p $pid /path/to/protons/wine". The wine path is something like "<installation directory of proton>/files/bin/wine64".
In the meantime DXR was also finally enabled by default in vkd3d-proton (https://github.com/HansKristian-Work/vkd3d-proton/pull/1766) 
@pixelcluster Nice, that's good to know. Do you know why/how adding the wine path in that way helps?
@nh I'm not 100% sure, but I think what might be happening is that gdb tries to look for address space layout info in the Windows PE file (which isn’t ELF, so it fails, so gdb has no way of knowing where code/data/etc are and gives up). The wine64 binary is ELF, so instructing gdb to use that file instead fixes the issue.
@pixelcluster @nh Heh. Good story.
Printf (partly) to the rescue!