Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>, John Wolfe <jlw@caldera.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: Petr Sorfa's Dwarf 2 changes
Date: Mon, 04 Nov 2002 12:25:00 -0000	[thread overview]
Message-ID: <20021104202641.GA7194@nevyn.them.org> (raw)
In-Reply-To: <vt2fzuhje0y.fsf@zenia.red-bean.com>

On Mon, Nov 04, 2002 at 03:06:21PM -0500, Jim Blandy wrote:
> 
> Andrew Cagney <ac131313@redhat.com> writes:
> > > I'm undertaking some related work in dwarf2read.c which will almost
> > > certainly conflict with Caldera's changes, and I'd like to see where
> > > you guys ended up.
> > 
> > Care to expand?
> 
> Sure --- I'm trying to put together a patch to support
> inter-compilation unit die references, which is (the hardest?) part of
> supporting Dwarf 2 compression.
> 
> I think the changes are going to be pretty widespread.
> 
> At the moment, dwarf2read.c has a number of global variables that
> describe per-compilation-unit things.  These get set as we do the
> psymtab scan, stashed in each psymtab we create, and then restored
> each time we convert a psymtab to a symtab.  If we're going to handle
> inter-CU references, we're going to be dealing with more than one CU
> at a time, so that's not going to be sufficient any more --- which CU
> you need depends on which die you're looking at.
> 
> I'd like to change GDB to have a per-objfile Dwarf-specific structure
> (like struct dbx_symfile_info for STABS), and per-CU Dwarf-specific
> structures.  These would be passed as arguments amongst the
> dwarf2read.c functions as appropriate.  Furthermore, each die might
> need to have a pointer to the CU that owns it.
> 
> Those are pretty pervasive changes, but I think the folks who have
> worked in dwarf2read.c will agree that they're the right way to go.
> When I've gotten something working on the branch I'll have more
> perspective on what's really needed.

Not only will they agree, I believe Petr and John had already finished
doing this.  Doubtless there's still some room for improvement, but the
functionality is there...  John, do you have that merged dwarf2read
available?

[For instance, from Petr's July posting:
        * dwarf2read.c (build_die_ref): New function that builds
          a new die reference if necessary, will search across
          multiple comp units to find the reference.
          (find_die_ref): New function that searches for a die
          reference for a given comp unit.
          (find_cu_header_from_begin_offset): New function that
          searches through a link list of comp unit headers for
          a comp unit that matches the given offset.
 ]

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-11-04 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 10:39 Jim Blandy
2002-10-23 11:48 ` Andrew Cagney
2002-11-04 12:21   ` Jim Blandy
2002-11-04 12:25     ` Daniel Jacobowitz [this message]
2002-11-04 12:38       ` Daniel Berlin
2002-11-04 12:50         ` Daniel Jacobowitz
2002-11-05  9:20         ` Jim Blandy
2002-11-05  9:18       ` Jim Blandy
2002-10-23 11:37 John Wolfe
2002-11-06  7:34 John Wolfe

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=20021104202641.GA7194@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=jlw@caldera.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