From: "Jim Blandy" <jimb@red-bean.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: "Carlos O'Donell" <carlos@codesourcery.com>,
brobecker@adacore.com, pedro@codesourcery.com,
gdb-patches@sourceware.org, dave.anglin@nrc.ca
Subject: Re: arm_addr_bits_remove
Date: Fri, 25 Jan 2008 22:14:00 -0000 [thread overview]
Message-ID: <8f2776cb0801251323h3283932dq96bb3aab41d0ca8c@mail.gmail.com> (raw)
In-Reply-To: <200801251849.m0PIncQu004356@hiauly1.hia.nrc.ca>
On Jan 25, 2008 10:49 AM, John David Anglin <dave@hiauly1.hia.nrc.ca> wrote:
> Regarding symbol tables, I would have to check what the two bits are
> used for. What struct/bits?
Within GDB, the debug info readers call record_line to add each source
location / pc mapping they find to GDB's internal tables. The issue
at hand is that record_line currently calls gdbarch_addr_bits_remove
on the pc values it's passed before recording them; apparently some
debug info had extra bits set in the addresses in the line number
info. Since this doesn't meet the spec (of either DWARF or STABS),
it's a bug in the producer; the call to gdbarch_addr_bits_remove is
meant to work around that bug. We've been discussing removing that
call, since it has caused problems recently.
next prev parent reply other threads:[~2008-01-25 21:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 21:17 arm_addr_bits_remove Pedro Alves
2008-01-22 23:26 ` arm_addr_bits_remove Jim Blandy
2008-01-23 14:45 ` arm_addr_bits_remove Pedro Alves
2008-01-23 19:22 ` arm_addr_bits_remove Jim Blandy
2008-01-23 19:29 ` arm_addr_bits_remove Daniel Jacobowitz
2008-01-23 21:12 ` arm_addr_bits_remove Jim Blandy
2008-01-24 4:54 ` arm_addr_bits_remove Pedro Alves
2008-01-24 7:35 ` arm_addr_bits_remove Jim Blandy
2008-01-24 6:30 ` arm_addr_bits_remove Jim Blandy
2008-01-24 13:39 ` arm_addr_bits_remove Pedro Alves
2008-01-24 14:45 ` arm_addr_bits_remove Daniel Jacobowitz
2008-01-24 14:56 ` arm_addr_bits_remove Pedro Alves
2008-01-24 16:53 ` arm_addr_bits_remove Jim Blandy
2008-01-24 17:01 ` arm_addr_bits_remove Pedro Alves
2008-01-24 22:19 ` arm_addr_bits_remove Joel Brobecker
2008-01-25 0:11 ` arm_addr_bits_remove Pedro Alves
2008-01-25 4:13 ` arm_addr_bits_remove Joel Brobecker
2008-01-25 9:56 ` arm_addr_bits_remove Carlos O'Donell
2008-01-25 21:24 ` arm_addr_bits_remove John David Anglin
2008-01-25 22:14 ` Jim Blandy [this message]
2008-01-26 13:57 ` arm_addr_bits_remove John David Anglin
2008-02-04 10:16 ` arm_addr_bits_remove Maciej W. Rozycki
2008-02-04 13:41 ` arm_addr_bits_remove Daniel Jacobowitz
2008-02-04 14:45 ` arm_addr_bits_remove Maciej W. Rozycki
2008-02-04 14:51 ` arm_addr_bits_remove Daniel Jacobowitz
2008-02-04 15:20 ` arm_addr_bits_remove Maciej W. Rozycki
2008-01-24 17:18 ` arm_addr_bits_remove Mark Kettenis
2008-01-24 17:50 ` arm_addr_bits_remove Joel Brobecker
2008-01-24 21:33 ` arm_addr_bits_remove 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=8f2776cb0801251323h3283932dq96bb3aab41d0ca8c@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=brobecker@adacore.com \
--cc=carlos@codesourcery.com \
--cc=dave.anglin@nrc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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