From: nickrob@snap.net.nz (Nick Roberts)
To: Baoqiu Cui <cbaoqiu@yahoo.com>, 3585@emacsbugs.donarmstrong.com
Cc: gnu-emacs-bug@moderators.isc.org
Subject: bug#3585: gdb not responding on Emacs from CVS
Date: Mon, 22 Jun 2009 00:47:51 +1200 [thread overview]
Message-ID: <19006.11255.5188.858625@totara.tehura.co.nz> (raw)
In-Reply-To: <bycr5xjc0xu.fsf@muchbodyking-lm.gateway.2wire.net>
> Here is some more information. It seems that this problem has something
> to do with the size of the program that I am trying to debug. If I try
> to follow the same steps for a small testing program, everything is
> fine.
>
> I noticed that, for the big program that I was debugging, it took about
> 50 seconds to have the "[initializing...]" Debugger status in mode-line
> changed to "[ready]". GDB simply does not respond to user's commands
> before it is *ready*.
>
> I tried the same thing on Emacs 21, which does not report status like
> [initializing...] or [ready], and it seems that GDB interface there is
> much faster. It only takes 10-15 seconds to load the same big program
> and then display the "(gdb) " prompt. Once the prompt is displayed, GDB
> is *ready* to respond any command I type in.
>
> Why does it take 50 seconds to "initialize" things? Emacs 22 seems to
> have the same "delay". Is there anyway to cut the time spent on
> initializing?
Emacs 22 builds a list of filenames from GDB that were used to build the
executable and this takes a long time if you have an executable that was
created from a large number of files, particularly if you use stabs debug
format. There is an option, gdb-create-source-file-list, which when set to
nil means that Emacs doesn't build this list at start up. That makes it
quicker but if there are relevant files in existing buffers or you visit them
they won't be enabled for debugging, e.g., you won't be able to click in the
fringe to set a breakpoint until execution has already stopped there.
This option has been around since 2008-07-01. If your Emacs predates this then
you might like to get Emacs 23.1 which will be released shortly.
Alternatively you can get the Emacs 21 speed/behavior by using M-x gud-gdb.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2009-06-21 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 2:57 bug#3585: gdb not responding on Emacs from CVS Baoqiu Cui
2009-06-16 12:58 ` Nick Roberts
[not found] ` <mailman.714.1245158249.2239.bug-gnu-emacs@gnu.org>
2009-06-16 17:00 ` Baoqiu Cui
[not found] ` <mailman.720.1245172650.2239.bug-gnu-emacs@gnu.org>
2009-06-16 21:40 ` Baoqiu Cui
2009-06-21 12:47 ` Nick Roberts [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=19006.11255.5188.858625@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=3585@emacsbugs.donarmstrong.com \
--cc=cbaoqiu@yahoo.com \
--cc=gnu-emacs-bug@moderators.isc.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.