From: asm warrior <asmwarrior@gmail.com>
To: gdb@sourceware.org
Subject: Slowdown of the response from the command line?
Date: Fri, 26 Feb 2010 16:48:00 -0000 [thread overview]
Message-ID: <9a806f981002251623w62282343i4553def7df4404ab@mail.gmail.com> (raw)
Hi, all.
I have just find a noticeable time delay when I enter a command line.
I'm debugging a DLL file under Windows, using
http://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/GDB-7.0.50.20100202/gdb-7.0.50.20100202-mingw32-bin.tar.gz/download
When I try to view the wxString value in a DLL, I entered this command to GDB
output /c m_Str.m_pchData[0]@((wxStringData*)m_Str.m_pchData - 1)->nDataLength
But it takes several seconds to give the answer returned from GDB.
I built the latest snapshot of
branch/gdb-weekly-7.0.90.20100223.tar.bz2 and
current/gdb-7.1.50.20100223, but the delay still exists.
In fact, this delay does *not* exist before, at least in the
http://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/GDB-7.0.1/gdb-7.0.1-mingw32-bin.tar.gz/download,
which is release in 20100107, In this version, the response from GDB
is really fast.
I have check the commit log from 20100107 to 20100202, I personally
suspect there's regression in the CLI of handing command input
c_expression.
Also, I have create a bug report here :
http://sourceware.org/bugzilla/show_bug.cgi?id=11316
Does anyone experience this time delay? Thanks
next reply other threads:[~2010-02-26 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 16:48 asm warrior [this message]
2010-02-26 22:12 ` Tom Tromey
2010-03-04 7:24 ` Asm_gmail
2010-03-04 11:21 ` Chris Sutcliffe
2010-03-04 12:01 ` asm warrior
2010-03-04 14:12 ` asm warrior
2010-03-05 2:13 ` Chris Sutcliffe
2010-03-05 2:45 ` Asm_gmail
2010-03-04 18:43 ` 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=9a806f981002251623w62282343i4553def7df4404ab@mail.gmail.com \
--to=asmwarrior@gmail.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