From: Paul Smith <paul@mad-scientist.net>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: [GDB 7.6/GCC 4.8.0] Slowdown in GDB macro processing for cores?
Date: Tue, 28 May 2013 15:25:00 -0000 [thread overview]
Message-ID: <1369754705.3295.8.camel@pdsdesk> (raw)
In-Reply-To: <1369264444.7209.184.camel@homebase>
On Wed, 2013-05-22 at 19:14 -0400, Paul Smith wrote:
> On Wed, 2013-05-22 at 14:12 -0600, Tom Tromey wrote:
> > >>>>> "Paul" == Paul Smith <psmith@gnu.org> writes:
> >
> > Paul> The interesting thing is both versions are constantly seeking and
> > Paul> reading to exactly the same location, over and over again. However GDB
> > Paul> 4.6 does it many times more than GDB 7.5.1. For example, I get this
> > Paul> combo:
>
> I have gmon.out from the last "fast" commit and the first "slow" commit;
> I reduced the number of iterations in the macro to 4 (instead of 200) so
> the slow one would not take so long :-).
>
> At this point I'm out of ideas. Please let me know if there's more
> you'd like me to do...
Hi all. I think I'm going to have to back up to GDB 7.5.1; the pain is
too great, when it does happen.
I'll maintain the core file and test setup, so let me know if there's
anything else I can do to help resolve this issue, or if there are
patches you'd like me to try.
Cheers!
prev parent reply other threads:[~2013-05-28 15:25 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
2013-05-28 17:53 ` Paul Smith
2013-05-28 18:03 ` Doug Evans
2013-05-28 15:25 ` Paul Smith [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=1369754705.3295.8.camel@pdsdesk \
--to=paul@mad-scientist.net \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--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