This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Possible gcc/DWARF or gdb/DWARF problem
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: fnf at ninemoons dot com
- Cc: gcc-bugs at gcc dot gnu dot org, gdb at sources dot redhat dot com
- Date: Sun, 30 Nov 2003 20:54:31 -0500
- Subject: Re: [RFC] Possible gcc/DWARF or gdb/DWARF problem
- References: <200311292026.hATKQ3OI025805@fred.ninemoons.com>
On Sat, Nov 29, 2003 at 01:26:03PM -0700, Fred Fish wrote:
> I'd like to get some comments on whether this is a gcc/DWARF or
> gdb/DWARF issue. If the consensus is that gdb is not doing the right
> thing, then I'll chase the problem in gdb. If the consensus is that
> it is gcc, then I'll file a formal gcc bug report. My guess is that
> since gcc is generating the memory offset of a 1 byte object relative
> to the frame pointer that the DW_AT_location for the big endian case
> should be:
>
> DW_AT_location DW_OP_fbreg 3
I agree. We're describing an object in memory of size 1. It should be
at the specified location, not padded.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer