From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] classes, partial symtabs, and DW_AT_specification
Date: Wed, 28 Jan 2004 19:59:00 -0000 [thread overview]
Message-ID: <20040128195939.GA15632@nevyn.them.org> (raw)
In-Reply-To: <yf24qufewk7.fsf@hawaii.kealia.com>
On Wed, Jan 28, 2004 at 10:51:20AM -0800, David Carlton wrote:
> Yeah. For the issue I ran into, it's probably not _too_ hard to
> solve: we could build up a die->parent table that only covered the
> dies that we would want to parse while reading the psymtabs - the spec
> die that I'm looking for should already be such a die. But using this
> as an excuse to step back and think about how we want dwarf2 psymtabs
> to work in an ideal world would certainly be a good idea.
Hmm, that is an interesting idea. It may be worthwhile.
> > With a little tuning, I think this is a solvable problem. It will
> > probably take a speed hit, but smaller debug info will hopefully
> > make up for a lot of that. And then, if someone implements
> > .debug_info_index, we can use that for psymtabs instead.
>
> Do you have a reference for .debug_info_index? I tried searching for
> it, but nothing turned up; I couldn't find an archive for the dwarf2
> mailing list.
There's no archive. Someone, IIRC Jim, proposed it before I joined the
dwarf2 list; the basic concept is that it's exactly the same format as
.debug_info, but with less information.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-28 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 0:41 David Carlton
2004-01-25 17:00 ` Daniel Jacobowitz
2004-01-28 18:51 ` David Carlton
2004-01-28 19:59 ` Daniel Jacobowitz [this message]
2004-01-28 17:11 ` Elena Zannoni
2004-01-28 18:44 ` David Carlton
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=20040128195939.GA15632@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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