From: Daniel Jacobowitz <drow@mvista.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: dwarf2_get_pc_bounds problem
Date: Fri, 14 Feb 2003 15:12:00 -0000 [thread overview]
Message-ID: <20030214151227.GB30416@nevyn.them.org> (raw)
In-Reply-To: <1045220381.25349.10.camel@Dragon>
On Fri, Feb 14, 2003 at 02:59:40AM -0800, Martin M. Hunt wrote:
> I'm investigating several errors in recent versions of gdb and they all
> seem to be caused by bogus values for lowpc and highpc returned from
> dwarf2_get_pc_bounds(). I'm not a DWARF expert so maybe the problem is
> bad debug info, but the code in dwarf2_get_pc_bounds seems suspicious.
>
> What I'm seeing is that with a program linked at 0x80000000, all the
> highpc and lowpc look fine, except those derived from DW_AT_ranges
> information. Those are all very small, like 0x100. Looking at the code
> in dwarf2_get_pc_bounds(), most of it seems to be trying to calculate a
> variable "base" which is then never used. Perhaps a simple addition was
> left out?
Ah, er, um, er.... I tested this, how the heck did it work? Aha, my
test case involved multiple sections, so GCC used a base of 0. That's
how.
Could you try this obvious fix? Still doesn't fix Jakub's test (we
really do need discontiguous ranges for that to work) but r_type
searches one local block instead of going straight to the function.
Oddly, I remember this happening before. I may have lost the addition
in a merge somewhere.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-02-14 Daniel Jacobowitz <drow@mvista.com>
* dwarf2read.c (dwarf2_get_pc_bounds): Offset addresses by base.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.85
diff -u -p -r1.85 dwarf2read.c
--- dwarf2read.c 4 Feb 2003 20:17:02 -0000 1.85
+++ dwarf2read.c 14 Feb 2003 15:10:24 -0000
@@ -2195,6 +2195,9 @@ dwarf2_get_pc_bounds (struct die_info *d
return 0;
}
+ range_beginning += base;
+ range_end += base;
+
/* FIXME: This is recording everything as a low-high
segment of consecutive addresses. We should have a
data structure for discontiguous block ranges
next prev parent reply other threads:[~2003-02-14 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 10:59 Martin M. Hunt
2003-02-14 15:12 ` Daniel Jacobowitz [this message]
2003-02-14 19:01 ` Martin M. Hunt
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=20030214151227.GB30416@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=hunt@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