From: Doug Evans <xdje42@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch 0/2] Accelerate symbol lookups 15x
Date: Fri, 24 Oct 2014 07:19:00 -0000 [thread overview]
Message-ID: <CAP9bCMQsjac4uu08F-N0DQTz+AY9Lpzt=M=RKBDFRUW2CbEzCg@mail.gmail.com> (raw)
In-Reply-To: <20141020214410.GA22011@host2.jankratochvil.net>
On Mon, Oct 20, 2014 at 2:44 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> Hi,
>
> this patchset has been developed+tested only on top of
> [patchv2] Fix 100x slowdown regression on DWZ files
> https://sourceware.org/ml/gdb-patches/2014-10/msg00031.html
>
> [...]
> g++ -o slow slow.C -Wall -g $(pkg-config --libs gtkmm-3.0)
> gdb ./slow -ex 'b C::m' -ex 'maintenance set per-command space' -ex 'maintenance set per-command symtab' -ex 'maintenance set per-command time' -ex r
> [...]
> (gdb) p <tab><tab>
> Display all 183904 possibilities? (y or n) n
> (gdb) p/r var
Sorry I didn't mention this sooner. I wanted to point this out since
it's a more straightforward way to expand symtabs. Instead of using
"p <tab><tab>" to expand symtabs, there is "mt expand-symtabs".
prev parent reply other threads:[~2014-10-24 7:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 21:44 Jan Kratochvil
2014-10-22 8:55 ` Doug Evans
2014-10-23 18:24 ` [patchv2 2/2] Accelerate lookup_symbol_aux_objfile 14.5x [Re: [patch 0/2] Accelerate symbol lookups 15x] Jan Kratochvil
2014-10-24 7:16 ` Doug Evans
2014-10-24 7:33 ` Jan Kratochvil
2014-10-24 16:07 ` Doug Evans
2014-10-27 5:55 ` Doug Evans
2014-10-27 6:02 ` Doug Evans
2014-10-27 8:54 ` Jan Kratochvil
2014-11-29 12:11 ` [patchv3 2/2] Accelerate lookup_symbol_aux_objfile 85x Jan Kratochvil
2014-12-02 3:07 ` Doug Evans
2014-12-03 18:05 ` Jan Kratochvil
2014-12-04 6:21 ` Doug Evans
2014-12-04 7:27 ` [commit] " Jan Kratochvil
2014-10-22 8:57 ` [patch 0/2] Accelerate symbol lookups 15x Doug Evans
2014-10-24 7:19 ` Doug Evans [this message]
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='CAP9bCMQsjac4uu08F-N0DQTz+AY9Lpzt=M=RKBDFRUW2CbEzCg@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).