https://bugs.winehq.org/show_bug.cgi?id=57308
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #2 from Bernhard Übelacker bernhardu@mailbox.org --- (In reply to Rafał Mużyło from comment #1)
...yeah, about that: on Linux that usually works though an ELF tag; libs under x86_64-windows are cross-compiled Windows DLLs - those use different mechanism and I wouldn't be surprised if - if anything like that is even possible (it might be) - the files with symbols needed to be in the same path as their libs, perhaps even mandatorily in pdb format.
:shrug: Gentoo skips stripping dlls, only doing it with ELF libraries.
I guess in this context an example could be Cygwin, as it looks like it provides stripped PEs, and separate debug symbols, without using PDBs:
https://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_6... - usr/bin/ls.exe ls.exe: PE32+ executable (console) x86-64, for MS Windows, 12 sections
https://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_6... - usr/lib/debug/usr/bin/ls.exe.dbg ls.exe.dbg: PE32+ executable (console) x86-64, for MS Windows, 21 sections
But I guess due to the connected archlinux issue this wine bug is not about splitting the debug info, instead really about winedbg searching with a strange path?
If I read it right a start for some experimenting could be to create a single split dll by: - copy dll to dll.debug and "objcopy --only-keep-debug" on it - strip the original dll