> When I start gdb in emacs, 'top' shows that gdb is running at about 50% CPU
> for more than a minute and then the load goes slowly down to a value below
> 1%. This takes about 2 minutes. Another thing that is a bit odd is, that
> the gdb prompt in emacs appears after about 15 seconds, which makes the
> user think that emacs/gdb is ready. But when I enter e.g. 'h RET', I have
> to wait for nearly 2 minutes till the help output is printed.
Previously you said:
gdb --fullname <image-name> core and then "up" or "bt" in gdb takes a
bit more than 20 seconds, whereas gdba -annotate=3 <image-name> core
and then "up" or "bt" needs 2 and a half minutes.
Which part takes the long time "gdb --annotate=3 <image-name> core" or "up"?
It sounds like it might be the first bit. If it is:
Does "gdb --annotate=3 <image-name>" take as long?
The only command that I can think that might take a long time at start up
is gdb-set-gud-minor-mode-existing-buffers (or ...buffers-1 depending on
your version of GDB. Which version are you running?) if you have a lot
of sources/buffer open.
Can you set gdb-enable-debug to to t, start GDB and post the values of
gdb-debug-ring to emacs-devel, if it's not too big/sensitive (you can post
this to me directly if you like).
--
Nick http://www.inet.net.nz/~nickrob
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
