This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: arm_addr_bits_remove
- From: "Jim Blandy" <jimb at red-bean dot com>
- To: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Cc: "Carlos O'Donell" <carlos at codesourcery dot com>, brobecker at adacore dot com, pedro at codesourcery dot com, gdb-patches at sourceware dot org, dave dot anglin at nrc dot ca
- Date: Fri, 25 Jan 2008 13:23:38 -0800
- Subject: Re: arm_addr_bits_remove
- References: <47996465.6090201@codesourcery.com> <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.