From: "Martin M. Hunt" <hunt@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: DWARF2 line number problem
Date: Wed, 21 Aug 2002 10:38:00 -0000 [thread overview]
Message-ID: <200208211038.03163.hunt@redhat.com> (raw)
In-Reply-To: <vt2d6scoku0.fsf@zenia.red-bean.com>
On Tuesday 20 August 2002 10:13 pm, you wrote:
> "Martin M. Hunt" <hunt@redhat.com> writes:
> > I have a problem and I'm not sure what the correct solution would be.
> >
> > I'm looking at gcc mips output. The compilation unit says pointer
> > size is 4, but the DWARF line section is setting the address to a
> > sign-extended 8-byte value. GDB cleverly ignores the actual size of
> > the extended opcode and reads a 4-byte value then starts parsing the
> > rest of the bytes as line opcodes!
>
> Could you compile your program with -save-temps -dA, and post the
> assembly code?
I'll send it to you if you want, but the problem is not there.
The problem appears to be either GAS or GDB depending on how we interpret the
DWARF spec.
GAS calculates the size of addresses to put in the line table from
bfd_arch_bits_per_address() which returns 64 even though in the case of o32
we are using a 32-bit ABI. gas is passed "-32" on its command line, so
perhaps it should be using this?
I am wondering why no one else has run into this problem? Maybe I am missing
something?
--
Martin Hunt
GDB Engineer
Red Hat, Inc.
next prev parent reply other threads:[~2002-08-21 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 21:56 Martin M. Hunt
2002-08-20 22:24 ` Jim Blandy
2002-08-21 10:38 ` Martin M. Hunt [this message]
2002-08-21 10:57 ` Jim Blandy
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=200208211038.03163.hunt@redhat.com \
--to=hunt@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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