From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Split ELF Debug (default or not?)
Date: Sun, 27 Nov 2005 17:24:57 -0500 [thread overview]
Message-ID: <1133130297.5317.504.camel@localhost> (raw)
In-Reply-To: <1133125287.7388.4.camel@home.yosifov.net>
On Sun, 2005-11-27 at 23:01 +0200, Ivan Yosifov wrote:
> On Sun, 2005-11-27 at 11:55 -0500, Ned Ludd wrote:
> > On Sun, 2005-11-27 at 10:44 -0500, Ned Ludd wrote:
> > > On Sun, 2005-11-27 at 15:22 +0000, Edward Catmur wrote:
> > > > On Sun, 2005-11-27 at 08:40 -0500, Ned Ludd wrote:
> > > > > On Sun, 2005-11-27 at 15:09 +0200, Ivan Yosifov wrote:
> > > > > > And one more thing. For proper debugging, don't I need the source to be
> > > > > > present ?
> > > > >
> > > > > -g3 -ggdb embeds the source code in the debug info so I don't see the
> > > > > point.
> > > >
> > > > It doesn't; at least not with gcc 3.4.4. It does embed function
> > > > prototypes and macro definitions, though.
> > > >
> > > > Ed Catmur
> > >
> > > Eh?
> >
> >
> > Never mind you were right Ed. taviso pointed out that dwarf2 doesnt
> > support embedding the actual source. I was seeing the source due to me
> > not having deleted the source.
> >
> > Guess that is where the debugedit thing of Tester's would come in handy
> > on glibc hosts.
>
> What is this debugedit thing for us non-devs ? IMO portage should have
> some way to keep the sources around for debugging, for the patch you are
> proposing to be fully useful.
Having the source around or not does not make the splitdebug feature any
less useful. debugedit would however enhance some aspects of debugging.
See the comments posted at the top of this thread from tester@gentoo on
debugedit.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-27 22:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 17:50 [gentoo-dev] Split ELF Debug (defult or not?) Ned Ludd
2005-11-26 18:30 ` 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 [this message]
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=1133130297.5317.504.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