From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb@sources.redhat.com>
Subject: Re: A hack for DW_FORM_ref_addr
Date: Thu, 31 Jul 2003 18:29:00 -0000 [thread overview]
Message-ID: <20030731182857.GB14520@lucon.org> (raw)
In-Reply-To: <20030731182219.GA9271@nevyn.them.org>
On Thu, Jul 31, 2003 at 02:22:19PM -0400, Daniel Jacobowitz wrote:
> On Thu, Jul 31, 2003 at 09:16:19AM -0700, H. J. Lu wrote:
> > On Wed, Jul 30, 2003 at 10:16:53PM -0700, H. J. Lu wrote:
> > > > >
> > > > > 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.
> > >
> > >
> >
> > FYI, this is the hack I am going to try.
>
> It may be safe, but it's unacceptable. Take a look at the memory usage
> requirements for -readnow, if libc.so.6 has debugging information.
> You've just eaten probably 200MB of RAM.
>
Since DW_FORM_ref_addr requires it, I don't see there is an easy way
out. I guess I could only save those used by DW_FORM_ref_addr.
H.J.
next prev parent reply other threads:[~2003-07-31 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 21:42 DW_FORM_ref_addr dosn't work 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
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 [this message]
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=20030731182857.GB14520@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).