From: "Martin M. Hunt" <hunt@redhat.com>
To: gdb@sources.redhat.com
Subject: dwarf2_get_pc_bounds problem
Date: Fri, 14 Feb 2003 10:59:00 -0000 [thread overview]
Message-ID: <1045220381.25349.10.camel@Dragon> (raw)
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?
Martin
next reply other threads:[~2003-02-14 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 10:59 Martin M. Hunt [this message]
2003-02-14 15:12 ` Daniel Jacobowitz
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=1045220381.25349.10.camel@Dragon \
--to=hunt@redhat.com \
--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