This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Re: Section .debug_info in object file

From: Elias Athanasopoulos <eathan at otenet dot gr>
To: Richard Henderson <rth at redhat dot com>
Cc: Pierre Habraken <Pierre dot Habraken at imag dot fr>, binutils at sources dot redhat dot com, gdb at sources dot redhat dot com, Richard dot Earnshaw at arm dot com
Date: Fri, 13 Sep 2002 01:13:06 +0300
Subject: Re: [PATCH] Re: Section .debug_info in object file
References: <3D806189.7A45FCBA@imag.fr> <20020912220303.A1134@neutrino.particles.org> <20020912205434.GA20375@redhat.com>

On Thu, Sep 12, 2002 at 01:54:34PM -0700, Richard Henderson wrote:
> On Thu, Sep 12, 2002 at 10:03:03PM +0300, Elias Athanasopoulos wrote:
> > 	* dwarf2dbg.c (out_debug_abbrev): Add support for the DW_AT_name field.
> > 	(out_debug_info): Likewise.
> 
> I suppose we could do something like this.
> 
> But it seems to me that this is a gdb bug.  The complete file+line
> mapping is available in .debug_line.  What purpose does the AT_name
> field of the compilation unit serve?

Maybe gdb can grab the info from .debug_line, but still gcc uses 
DW_AT_name for (every) C source file and this conflicts with gas which 
skips this field (readelf, as I wrote, produces garbage). 

Elias

-- 
http://gnewtellium.sourceforge.net			MP3 is not a crime.

References:
- Section .debug_info in object file
  - From: Pierre Habraken
- [PATCH] Re: Section .debug_info in object file
  - From: Elias Athanasopoulos
- Re: [PATCH] Re: Section .debug_info in object file
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]