Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, ccoutant@google.com
Subject: Re: [RFA] Add global/static and symbol kind indicator to .gdb_index
Date: Sat, 23 Jun 2012 22:25:00 -0000	[thread overview]
Message-ID: <CADPb22QjjtgUiVTmO+MVdG+=tsOj0TmjOB6rBJDpGhAUCR0ZAw@mail.gmail.com> (raw)
In-Reply-To: <87y5nfdpq7.fsf@fleche.redhat.com>

On Fri, Jun 22, 2012 at 2:02 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Doug> The global/static bit massively speeds up looking up things like
> Doug> "int" when debugging with lots of shared libraries (all having
> Doug> .gdb_index).  PR 14125
>
> Tom> I don't think this patch is needed to achieve this.  At least, the "int"
> Tom> case and other similar cases were fixed by:
>
> Doug pointed out on irc that I was mistaken here.
> The issue in his case is that, even though each individual index has a
> single entry for "int", there are still many indices, so gdb still does
> excessive CU expansion.
> I'm sorry for the error.
>
> Tom> I think it is ok.
>
> At least this part still seems correct ;-)
>
> Tom

Thanks.
Committed with this NEWS entry.


diff -u -p -r1.527 -r1.528
--- NEWS        6 Jun 2012 18:03:53 -0000       1.527
+++ NEWS        23 Jun 2012 22:23:46 -0000      1.528
@@ -112,6 +112,12 @@
   the ability to set breakpoints on inlined functions will be lost
   in symbol files with older .gdb_index sections.

+  The .gdb_index section has also been updated to record more information
+  about each symbol.  This speeds up the "info variables", "info functions"
+  and "info types" commands when used with programs having the .gdb_index
+  section, as well as speeding up debugging with shared libraries using
+  the .gdb_index section.
+
 * Ada support for GDB/MI Variable Objects has been added.

 * GDB can now support 'breakpoint always-inserted mode' in 'record'


  parent reply	other threads:[~2012-06-23 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  7:49 Doug Evans
2012-06-19 14:01 ` Pedro Alves
2012-06-19 16:08 ` Eli Zaretskii
2012-06-19 19:41   ` Doug Evans
2012-06-22 19:45 ` Tom Tromey
2012-06-22 21:03   ` Tom Tromey
2012-06-22 21:20     ` Cary Coutant
2012-06-23 19:59       ` Doug Evans
2012-06-25 14:53         ` Tom Tromey
2012-06-25 15:06       ` Tom Tromey
2012-06-23 22:25     ` Doug Evans [this message]
2012-06-24  8:09   ` Doug Evans

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='CADPb22QjjtgUiVTmO+MVdG+=tsOj0TmjOB6rBJDpGhAUCR0ZAw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=ccoutant@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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