From: Tom Tromey <tromey@redhat.com>
To: ppluzhnikov@google.com (Paul Pluzhnikov)
Cc: gdb@sourceware.org
Subject: Re: quadratic slowdown in 'where' command
Date: Sat, 03 Jan 2009 19:21:00 -0000 [thread overview]
Message-ID: <m38wpsryb8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081104235737.CD4763A6B0B@localhost> (Paul Pluzhnikov's message of "Tue\, 4 Nov 2008 15\:57\:37 -0800 \(PST\)")
>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
Paul> While debugging something else, I noticed extreme slowdown of
Paul> 'where' command for a deeply recursive stack trace, and was able
Paul> to reproduce it on a small example (below).
FWIW, I'm able to reproduce this as well.
Paul> The results are also rather interesting: running 'where' by hand
Paul> shows that GDB prints all levels except the last one rather fast,
Paul> but then 'freezes' for a long time printing the last level.
I wasn't able to reproduce this. That is, I ran the test a number of
times, and sometimes I saw this effect, but sometimes I did not.
Could you file this in bugzilla?
Tom
prev parent reply other threads:[~2009-01-03 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 23:58 Paul Pluzhnikov
2009-01-03 19:21 ` Tom Tromey [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=m38wpsryb8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.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