From: Doug Evans <dje@google.com>
To: psmith@gnu.org
Cc: Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>,
gdb <gdb@sourceware.org>
Subject: Re: [GDB 7.6/GCC 4.8.0] Slowdown in GDB macro processing for cores?
Date: Tue, 28 May 2013 17:40:00 -0000 [thread overview]
Message-ID: <CADPb22R78kWcCog5f0OV5sa-F6N08X_p92HSMSX+xy3Wf75q_w@mail.gmail.com> (raw)
In-Reply-To: <1369762373.3295.20.camel@pdsdesk>
On Tue, May 28, 2013 at 10:32 AM, Paul Smith <psmith@gnu.org> wrote:
> On Tue, 2013-05-28 at 10:10 -0700, Doug Evans wrote:
>> And I can't offhand explain why you *only* see the slowdown with a
>> core file and not with a live executable.
>
> Well, just because we haven't found a way to make it happen with live
> debugging doesn't mean it couldn't :-).
Indeed.
>> I wasn't aware of the problems with the 12/11/16 patch you found.
>> I've submitted a minor improvement - IMO the real fix will involve a
>> lot more effort - gdb's symbol handling is obtuse enough that it's
>> easy to introduce performance regressions or even overlook basic
>> performance problems.
>
> I'll try the latest Git to see if it makes a difference.
I'd be curious for before/after data with this patch:
http://sourceware.org/ml/gdb-patches/2013-05/msg00964.html
I doubt it fixes everything, or even a lot of it.
But data is good.
next prev parent reply other threads:[~2013-05-28 17:40 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
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 [this message]
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=CADPb22R78kWcCog5f0OV5sa-F6N08X_p92HSMSX+xy3Wf75q_w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=psmith@gnu.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