From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@ninemoons.com
Cc: gcc-bugs@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: [RFC] Possible gcc/DWARF or gdb/DWARF problem
Date: Mon, 01 Dec 2003 01:54:00 -0000 [thread overview]
Message-ID: <20031201015431.GA10708@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2003-12-01 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 20:26 Fred Fish
2003-12-01 1:54 ` Daniel Jacobowitz [this message]
2003-12-01 15:21 ` Jim Blandy
2003-12-01 16:42 ` Fred Fish
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=20031201015431.GA10708@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnf@ninemoons.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
/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