Adding debuginfo Support to Wine Makefiles
rob at codeweavers.com
Wed Nov 24 12:33:59 CST 2004
Mike Hearn wrote:
>On Wed, 24 Nov 2004 11:24:01 -0600, Robert Shearman wrote:
>>I want to add support generating .debug files that are linked from .so
>>files so that we can have one set of binaries, no matter whether a
>>person is a developer or end-user and yet have no additional disk space
>>or bandwidth costs.
>Cool. Though this does mean yet more packages on the web page.
Theoretically, you will only need the debuginfo packages if you have a
crash and want to debug it. It will not be something that most users
>Also this only works with gdb, no? And currently unless something truly
>terrible happens Wine will never core dump, it'll trap the exception and
>launch winedbg which I think does not support .gnu_debuglink
>Is the plan to add support for that to winedbg?
It is already there. I added support for it a few months ago.
>>This is really just a RFC about changes I've made to the DLL makefiles,
>>before I start copying and pasting them to the other areas. Am I on the
>>right lines here? Do I need to add a configure check for objcopy? Do I
>>need a configure check for the --add-gnu-debuglink option?
>Yes, this is a very recent feature only available in new toolchains. It
>only recently started stabilising too so it'd be nice if there was a way
>to disable it.
I wasn't very clear about what I wanted with the makefiles. Basically,
this will be an optional post-build step. The way I am leaning towards
at the moment is that "make install" will install with full debugging
information, but "make install && make install-debuginfo" will strip the
debug info into separate files and install it. AFAIK, the feature has
been stable for a year and a few distros are making full use of it.
Fedora definitely provides -debug packages that have the separate debug
More information about the wine-devel