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: Andi Kleen <andi at firstfloor dot org>
- Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org
- Date: Sat, 22 Dec 2007 20:20:26 -0500
- Subject: Re: Designs for better debug info in GCC
- References: <m34pec1x4k.fsf@localhost.localdomain.suse.lists.egcs> <orwsr8eyz5.fsf@oliva.athome.lsd.ic.unicamp.br.suse.lists.egcs> <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>
On Sat, Dec 22, 2007 at 11:49:23PM +0100, Andi Kleen wrote:
> > As I'm sure you know, the GNU
> > binutils
>
> Actually binutils only barely supports debuginfo. AFAIK
> objcopy is the tool tool that knows anything about them.
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.
> The Linux distributions have debuginfo rpms that work
> fine for that. But it does not solve the link time IO problem.
FWIW, in the paragraph you were responding to Ian was talking about
the Darwin system, not the GNU one.
--
Daniel Jacobowitz
CodeSourcery