From: Pedro Alves <palves@redhat.com>
To: psmith@gnu.org
Cc: gdb@sourceware.org
Subject: Re: [GDB 7.6/GCC 4.8.0] Slowdown in GDB macro processing for cores?
Date: Fri, 17 May 2013 10:15:00 -0000 [thread overview]
Message-ID: <51960329.2010802@redhat.com> (raw)
In-Reply-To: <1368733335.4101.743.camel@pdsdesk>
On 05/16/2013 08:42 PM, Paul Smith wrote:
> Hi all. Is anyone aware of an issue with a big slowdown running macros
> on core files? I'm not sure if this is related to GCC 4.8 or GDB 7.6,
> or what, but I'm seeing a 4x or more slowdown when running macros on
> core files from previous releases.
>
> Running against a live process is the same speed as before.
Wow.
If you haven't yet, it'd make sense to try process vs core at the
exact same spot:
$ gdb myprogram
(gdb) run
...
(gdb) mymacro
(gdb) gcore mycore
(gdb) quit
$ gdb myprogram -c mycore
(gdb) mymacro
> Against a core file it takes a second or longer per iteration of this
> loop! FWIW, the class this macro operates on is very large and contains
> a lot of data per object.
>
> Any ideas? Is there a handy way to tell where the slowdown is happening
> here?
I'm really surprised. If anything, I'd expect cores to be marginally faster.
I suggest git bisecting gdb looking. Maybe you'll find the culprit
easily that way.
> Should we just drop back to DWARF2 or DWARF3 (I haven't checked
> if that will help tho)?
Ideally no, of course. Let us know if that indeed helps.
Using DWARF < 4 should make it easier to git bisect the
culprit, as you can then start bisecting before the
patches that added support for DWARF4.
--
Pedro Alves
next prev parent reply other threads:[~2013-05-17 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 19:42 Paul Smith
2013-05-17 10:15 ` Pedro Alves [this message]
2013-05-22 18:50 ` Paul Smith
2013-05-22 19:20 ` Paul Smith
2013-05-22 20:12 ` Tom Tromey
2013-05-22 20:52 ` Paul Smith
2013-05-22 21:02 ` Paul Smith
2013-05-22 23:14 ` Paul Smith
2013-05-23 2:44 ` Doug Evans
2013-05-23 4:41 ` Paul Smith
2013-05-28 17:11 ` Doug Evans
2013-05-28 17:33 ` Paul Smith
2013-05-28 17:40 ` Doug Evans
2013-05-28 17:53 ` Paul Smith
2013-05-28 18:03 ` Doug Evans
2013-05-28 15:25 ` Paul Smith
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=51960329.2010802@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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