Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [1/4] RFC: refactor partial symbol tables
Date: Tue, 26 Jan 2010 21:54:00 -0000	[thread overview]
Message-ID: <m3vdeoh6r6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100126214550.GD17877@caradoc.them.org> (Daniel Jacobowitz's 	message of "Tue, 26 Jan 2010 16:45:50 -0500")

>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:

Daniel> Overall, I very much like this series and think it should go in.

Thanks.

Daniel> Have you considered the case of objfiles with multiple formats of
Daniel> debug info?  This used to be a very common case, where the system
Daniel> libraries had some stabs data and the user code had dwarf-2.  It's
Daniel> probably still happening on various platforms.  So it seems like
Daniel> we need to be able to query multiple symbol readers' qf functions,
Daniel> potentially.

I did consider this, and I (safely) punted.

On my branch, the only non-psymtab implementation of the quick API is in
dwarf2read.c, and that code bails out and reverts to using psymtabs if
it find that any other reader has created psymtabs for the objfile.

I'm not sure how hard it would be to do something nicer.  I didn't look
closely but I think that not all of the APIs compose nicely.

Tom


  reply	other threads:[~2010-01-26 21:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  0:25 Tom Tromey
2010-01-16  8:03 ` Eli Zaretskii
2010-03-09 22:22   ` Tom Tromey
2010-03-10  4:15     ` Eli Zaretskii
2010-03-10 18:46       ` Tom Tromey
2010-03-11 18:05     ` Stan Shebs
2010-03-12 18:35       ` Tom Tromey
2010-01-26 21:45 ` Daniel Jacobowitz
2010-01-26 21:54   ` Tom Tromey [this message]
2010-01-26 21:58     ` Daniel Jacobowitz
2010-01-26 22:06       ` Tom Tromey

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=m3vdeoh6r6.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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