This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Designs for better debug info in GCC
- From: Daniel Jacobowitz <drow at false dot org>
- To: gcc at gcc dot gnu dot org
- Date: Sat, 22 Dec 2007 20:36:03 -0500
- Subject: Re: Designs for better debug info in GCC
- References: <m3wsr76hov.fsf@localhost.localdomain.suse.lists.egcs> <or8x3ng5ie.fsf@oliva.athome.lsd.ic.unicamp.br.suse.lists.egcs> <m3r6hf4mw1.fsf@localhost.localdomain.suse.lists.egcs> <de8d50360712211607h77a0add5h794f6b5781b6491b@mail.gmail.com.suse.lists.egcs> <de8d50360712211609y643b8affpeb91048dedecbe60@mail.gmail.com.suse.lists.egcs> <7C283DB3-9716-4B2C-9721-D1F503B91CC4@apple.com.suse.lists.egcs> <m37ij64mwt.fsf@localhost.localdomain.suse.lists.egcs> <p73lk7me45o.fsf@bingen.suse.de> <20071223012025.GA15196@caradoc.them.org> <20071223013344.GA21843@one.firstfloor.org>
On Sun, Dec 23, 2007 at 02:33:44AM +0100, Andi Kleen wrote:
> > I don't know why you say that. ld knows a bit about debugging
> > sections, and how to read .debug_line for errors; objdump knows how to
> > decode debug info, as does readelf; strip knows how to remove it;
> > objcopy how to copy and separate it.
>
> Sorry I mean separate debuginfo, as Ian was refering too.
>
> I actually had a patch once to hack it into objdump for -S and
> also into addr2line but it was somewhat ugly and still
> had some problems and I didn't submit it.
Oh, I see. Yes, only BFD and GDB know much about it.
--
Daniel Jacobowitz
CodeSourcery