From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Split ELF Debug (defult or not?)
Date: Sat, 26 Nov 2005 12:50:30 -0500 [thread overview]
Message-ID: <1133027430.5317.307.camel@localhost> (raw)
Good afternoon,
probably in portage-2.0.54 a patch will be added to emit split debug
info. Having a split debug allows us to retain all the advantages of
stripping executables while gaining the ability to properly debug
executables in bfd aware programs. It's been in testing with a small
hand full of devs and works quite well, but before it's pushed in we
would like to get input from our devs & users.
Would you be willing to give up space in $ROOT/usr/lib/debug for ELF
executables by default in order to aid in better debugging by or do we
want to only emit it when a FEATURE= is defined.
Having a split debug pretty much obsoletes the need to add nostrip to
your features in order to get debug info.
Users wishing to not have debug info can simply add
INSTALL_MASK="/usr/lib/debug ${INSTALL_MASK}" to make.conf or the
environment unless we make it FEATURE based.
I'm in favor of it enabled per default but I'd like to know what you
think and why. (advantages of on/off by default etc..)
Anybody wanting to test or make use of this feature right away can grab
a copy of my prepstrip from
http://dev.gentoo.org/~solar/portage_misc/prepstrip and save it to
/usr/lib/portage/bin/prepstrip or patch portage with
http://dev.gentoo.org/~solar/patch_overlay/sys-apps/portage/portage-2.0.53_rc7-prepstrip.patch
It requires you merge pax-utils for the scanelf util.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-11-26 17:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 17:50 Ned Ludd [this message]
2005-11-26 18:30 ` [gentoo-dev] Split ELF Debug (defult or not?) Bruno
2005-11-26 18:55 ` [gentoo-dev] Split ELF Debug (default " Ned Ludd
2005-11-27 9:53 ` Kevin F. Quinn
2005-11-27 12:18 ` Ned Ludd
2005-11-26 19:15 ` [gentoo-dev] Split ELF Debug (defult " Olivier Crête
2005-11-26 19:20 ` [gentoo-dev] " R Hill
2005-11-27 12:24 ` [gentoo-dev] Re: Split ELF Debug (default " Ned Ludd
2005-11-27 13:09 ` Ivan Yosifov
2005-11-27 13:32 ` Edward Catmur
2005-11-27 13:40 ` Ned Ludd
2005-11-27 15:22 ` Edward Catmur
2005-11-27 15:44 ` Ned Ludd
2005-11-27 16:55 ` Ned Ludd
2005-11-27 21:01 ` Ivan Yosifov
2005-11-27 22:24 ` Ned Ludd
2005-11-28 11:00 ` Paul de Vrieze
2005-11-27 18:03 ` Mark Loeser
2005-11-27 19:51 ` Olivier Crête
2005-11-26 19:22 ` [gentoo-dev] Split ELF Debug (defult " Ivan Yosifov
2005-11-26 20:01 ` Mike Frysinger
2005-11-26 21:42 ` Petteri Räty
2005-11-27 0:48 ` Dan Meltzer
2005-11-27 0:53 ` Mart Raudsepp
2005-11-27 12:23 ` [gentoo-dev] Split ELF Debug (default " Ned Ludd
2005-11-26 23:10 ` [gentoo-dev] Split ELF Debug (defult " Luca Barbato
2005-11-27 12:54 ` Diego 'Flameeyes' Pettenò
2005-11-27 14:39 ` Dan Meltzer
2005-11-27 14:49 ` Diego 'Flameeyes' Pettenò
2005-11-27 14:50 ` Ned Ludd
2005-11-27 15:31 ` Edward Catmur
2005-11-28 1:18 ` Georgi Georgiev
2005-11-28 4:21 ` Edward Catmur
2005-11-27 15:04 ` Tavis Ormandy
2005-11-27 15:30 ` Dan Meltzer
2005-11-28 11:14 ` Paul de Vrieze
2005-11-27 22:35 ` Spider (D.m.D. Lj.)
2005-11-28 10:51 ` Paul de Vrieze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133027430.5317.307.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox