public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Daniel Jacobowitz <drow@false.org>,
	Cary Coutant <ccoutant@google.com>,
	Dodji Seketeli <dodji@redhat.com>,
	"GDB\/Archer list" <archer@sourceware.org>
Subject: Re: [RFC] Proposal for a new DWARF name index section
Date: Mon, 07 Dec 2009 21:32:00 -0000	[thread overview]
Message-ID: <m33a3m8o7t.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3ljhgdb1o.fsf@fleche.redhat.com> (Tom Tromey's message of "Sat, 05 Dec 2009 20:41:07 -0700")

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

Tom> Also, I made another funny hack tonight.  I changed gdb to read
Tom> .debug_aranges and .debug_gnu_index in a background thread.  This was
Tom> pretty easy to do; it really just few a couple global __thread
Tom> variables.  (I didn't attempt reading full symbols in a separate thread,
Tom> because that seems a lot more involved.)

BTW, what I mean by this is that when using the indices, sometimes GDB
has to read full symbols for a given CU.  This happens if we don't see
any index entry, or any aranges entry, for that CU.  In this situation
we can't tell whether that entry was somehow stripped or not created, or
just empty.

For aranges this is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42288
I updated the .debug_gnu_index PR with a similar request.

This sort of reading has to be done in the main thread.  There were just
too many problems with putting this into a separate thread -- not just
all the global variables, but this would also imply that users of the
symtabs would need to take a lock.

Tom> I'll clean up this patch a bit and push it to a new branch in archer
Tom> this week.

It is now on archer-tromey-threaded-dwarf.

Tom

  reply	other threads:[~2009-12-07 21:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10  9:04 Dodji Seketeli
2009-08-10 14:38 ` Jan Kratochvil
2009-08-10 17:36   ` Tom Tromey
2009-08-10 18:21     ` Jan Kratochvil
2009-08-11  7:55       ` Dodji Seketeli
2009-08-11 17:45         ` Jan Kratochvil
2009-08-11 22:43           ` Tom Tromey
2009-08-12 19:20             ` Jan Kratochvil
2009-08-11 22:29       ` Tom Tromey
2009-08-20 17:31 ` Dodji Seketeli
2009-11-17 23:46   ` Cary Coutant
2009-11-20 17:25     ` Tom Tromey
2009-11-22  4:39       ` Daniel Jacobowitz
2009-11-23 19:51         ` Tom Tromey
2009-12-01 19:14       ` Tom Tromey
2009-12-02  5:17         ` Daniel Jacobowitz
2009-12-02 17:07           ` Tom Tromey
2009-12-02 17:35             ` Daniel Jacobowitz
2009-12-02 19:23               ` Tom Tromey
2009-12-02 19:39                 ` Daniel Jacobowitz
2009-12-03  1:46                   ` Paul Pluzhnikov
2009-12-04 23:13                     ` Tom Tromey
2009-12-06  3:41                       ` Tom Tromey
2009-12-07 21:32                         ` Tom Tromey [this message]
2009-12-02 16:11         ` Dodji Seketeli
2009-12-02 17:29           ` Tom Tromey
2009-12-11 23:56     ` Tom Tromey
2009-12-12  0:06       ` Daniel Jacobowitz
2009-12-12  0:13       ` Cary Coutant
2009-12-13  3:48       ` Dodji Seketeli
2009-12-14 15:32       ` Dodji Seketeli

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=m33a3m8o7t.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=dodji@redhat.com \
    --cc=drow@false.org \
    --cc=ppluzhnikov@google.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).