From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: help-gnu-emacs@gnu.org, per.nordlow@gmail.com
Subject: Re: Sluggish Interface to GDB
Date: Sun, 30 Nov 2008 06:16:28 +0200 [thread overview]
Message-ID: <ud4gdg86b.fsf@gnu.org> (raw)
In-Reply-To: <18737.61202.82167.359075@kahikatea.snap.net.nz>
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 30 Nov 2008 14:40:34 +1300
> Cc: help-gnu-emacs@gnu.org
>
> This is too general to be a useful bug report unless it happens for all program
> that you debug. I don't see it debugging Emacs. It probably is Emacs that
> makes it slow but have you tried gdb on your program from the command line?
> What happens there? How deep is your stack? Have you got many watch
> expressions in the speed bar? large numbers of local variables? lots of extra
> RAM? which GUD related buffers to you have open?, etc, etc...
It might be a good idea to introduce an optional feature whereby GUD
would time-stamp the commands it sends to GDB and the responses it
gets. Then at least the time spent waiting for GDB would be instantly
visible.
prev parent reply other threads:[~2008-11-30 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 20:16 Sluggish Interface to GDB Nordlöw
2008-11-30 1:40 ` Nick Roberts
2008-11-30 4:16 ` Eli Zaretskii [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ud4gdg86b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=per.nordlow@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).