From: Srinath Avadhanula <srinathava@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Massive slowdown printing values in gdb-7.1
Date: Tue, 07 Sep 2010 01:23:00 -0000 [thread overview]
Message-ID: <AANLkTinM8RM5aKZH_6pfv1vFrcNhXsYd5EPWSixSZy93@mail.gmail.com> (raw)
In-Reply-To: <20100906233108.GB21706@adacore.com>
Hi Joel,
Thanks for the answer.
On Mon, Sep 6, 2010 at 7:31 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>
> I don't know if this might help, but have you tried gdb-7.2 and
> the CVS HEAD? gdb-7.2 and a daily snapshot of the development branch
> are both available at ftp://sourceware.org/pub/gdb/.
>
That did it! :) The latest from CVS: GNU gdb (GDB) 7.2.50.20100906
doesn't have this problem anymore.
Thanks a bunch :)
Srinath
next prev parent reply other threads:[~2010-09-07 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 23:27 Srinath Avadhanula
2010-09-06 23:31 ` Joel Brobecker
2010-09-07 1:23 ` Srinath Avadhanula [this message]
2010-09-07 1:36 ` Joel Brobecker
2010-09-07 2:18 ` Srinath Avadhanula
2010-09-07 16:24 ` Tom Tromey
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=AANLkTinM8RM5aKZH_6pfv1vFrcNhXsYd5EPWSixSZy93@mail.gmail.com \
--to=srinathava@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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