Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: lazy partial symbol table reading
Date: Wed, 25 Mar 2009 23:56:00 -0000	[thread overview]
Message-ID: <m33ad1yxpe.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090325223211.GH9472@adacore.com> (Joel Brobecker's message of "Wed\, 25 Mar 2009 15\:32\:11 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> I think I need to discuss the principle of this patch internally with
Joel> the other AdaCore GDB engineers, in particular with Paul Hilfinger.

Sounds good.

Joel> I think that this might impact Ada, because, when we do symbol lookups,
Joel> we need to search all psymtabs.

I see I did not touch any Ada files.  Oops, I'm sure that is going to
cause bugs.  But, it is always safe to just use ALL_PSYMTABS_REQUIRED
-- it just means that the benefit of laziness might be lost in some
scenario.

Perhaps it would have been better to make ALL_PSYMTABS, et al, call
require_partial_symbols, and then introduce new non-requiring variants
to be used where it is known to be ok.


Also on this topic... Jan reminded me today that in order to extend
laziness to symbol lookup, we'd have to get gcc to emit the
debug_pubnames section.  Actually emitting this is trivial (one line
change in gcc), but gcc also has bugs in its emission.  And, if we
want to preserve gdb's current symbol lookup style, we'd probably also
need to introduce a new debug_privnames.  (The issue is that "print x"
will work in gdb today if x is static -- but dwarf doesn't specify any
index for finding this.)

Tom


  reply	other threads:[~2009-03-25 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  0:31 Tom Tromey
2009-03-25 22:33 ` Joel Brobecker
2009-03-25 23:56   ` Tom Tromey [this message]
2009-03-26  1:24     ` Joel Brobecker
2009-07-20 21:36       ` 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=m33ad1yxpe.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.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