From: Daniel Jacobowitz <drow@false.org>
To: "Li, Rongsheng" <rongsheng.li@boeing.com>
Cc: gdb@sourceware.org
Subject: Re: GDB CLI speed
Date: Wed, 15 Mar 2006 14:25:00 -0000 [thread overview]
Message-ID: <20060315142312.GB12258@nevyn.them.org> (raw)
In-Reply-To: <7CA73FB7DA98FF4CB97739FFE1798B5A019460A0@XCH-SW-41.sw.nos.boeing.com>
On Tue, Mar 14, 2006 at 09:09:47PM -0800, Li, Rongsheng wrote:
>
> I am using gdb/ddd as the front end to run a large simulation and use
> the caned command files to confiure the simulation and typically I have
> a lot of "set" statements in the command file (thousands).
>
> One thing it bothers me is that it takes much longer for GDB CLI to
> execute these commands than DBX. Anyone of you outthere know what is the
> reason (especially in comparison against dbx) and a way to fix it ?
Sorry, this is too vague. What exactly are you doing that takes a long
time? How long is it taking?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-15 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 6:19 Li, Rongsheng
2006-03-15 14:25 ` Daniel Jacobowitz [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=20060315142312.GB12258@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rongsheng.li@boeing.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