From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb@sources.redhat.com>
Subject: Re: DW_FORM_ref_addr dosn't work
Date: Thu, 31 Jul 2003 05:16:00 -0000 [thread overview]
Message-ID: <20030731051653.GB1170@lucon.org> (raw)
In-Reply-To: <20030730215509.GA15640@nevyn.them.org>
On Wed, Jul 30, 2003 at 05:55:09PM -0400, Daniel Jacobowitz wrote:
> On Wed, Jul 30, 2003 at 02:52:27PM -0700, H. J. Lu wrote:
> > On Wed, Jul 30, 2003 at 05:45:03PM -0400, Daniel Jacobowitz wrote:
> > > On Wed, Jul 30, 2003 at 02:42:52PM -0700, H. J. Lu wrote:
> > > > DW_FORM_ref_addr can reference an entry in a different compilation
> > > > unit, even from a different shared object. But die_ref_table only
> > > > contains DIEs in one single compilation unit. Why do we do that? What
> > > > is the best way to fix it?
> > > >
> > > > BTW, I am enclosing my quick dirty hack for reference.
> > >
> > > Please read any of the thirty-some discussions of this in the list
> > > archives.
> > >
> > > I'm working on it in my spare time, of which I have not had enough to
> > > make much progress. The DWARF reader needs to be essentially
> > > rewritten.
> >
> > While waiting for your new DWARF reader, I will see how my hack
> > goes :-(.
>
> Since the die table is hashed by offset (isn't it?), presumably very
> badly.
It is OK for different compilation units within the same .debug_info
section.
H.J.
next prev parent reply other threads:[~2003-07-31 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 21:42 H. J. Lu
2003-07-30 21:45 ` Daniel Jacobowitz
2003-07-30 21:52 ` H. J. Lu
2003-07-30 21:55 ` Daniel Jacobowitz
2003-07-30 22:01 ` H. J. Lu
2003-07-31 5:16 ` H. J. Lu [this message]
2003-07-31 16:16 ` A hack for DW_FORM_ref_addr H. J. Lu
2003-07-31 18:22 ` Daniel Jacobowitz
2003-07-31 18:29 ` H. J. Lu
2003-07-31 22:33 ` Daniel Berlin
2003-07-31 21:21 ` H. J. Lu
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=20030731051653.GB1170@lucon.org \
--to=hjl@lucon.org \
--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