[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: lib/54449: _pic.a libraries contain unwanted debug information
The following reply was made to PR lib/54449; it has been noted by GNATS.
From: Christos Zoulas <christos%zoulas.com@localhost>
Andreas Gustafsson <gson%gson.org@localhost>
Subject: Re: lib/54449: _pic.a libraries contain unwanted debug information
Date: Mon, 12 Aug 2019 07:03:10 +0300
> upon consideration, i'm happy to be less strict about
> MKDEBUG=3Dyes builds, though i was reminded about my failed
> static debugging session a few months ago. does external
> debug info even work for .a?
Nope, I don't think it does (unless we change binutils).
> i think that means i'm ok with your other patch.
But I am not, because this means that DBG=3D-g will also not put symbols
in libfoo_pic.a (my patch will strip it). So I am inclined to leave it =
as it is
> i've never used the _g.a libraries. they alway seemed far
> annoying to build and use.
> i've simply had *all* my install have debug info. i only
> really switched to MKDEBUG when i noticed that huge-from-
> debug-info shlibs have a bad interaction with exec pages,
> and having it separate works around. (i'm now wishing, but
> hating myself for it, a build that gives me fat .a files
> with debug info, but skinny .so files with links to the
> debug info files. :)
Well, we should make MKDEBUG work properly. I don't
think we should be documenting DBG=3D (but also not breaking it).
Main Index |
Thread Index |