>>>>> "Nick" == Nick Roberts <[EMAIL PROTECTED]> writes:
Nick>
Nick> You might need to check that there aren't other buffers present
Nick> which just aren't visible.
I start emacs with option -Q and the buffer listing shows:
. * *gud-umc.vx* 1140 Debugger:run
*scratch* 0 Lisp Interaction
* *Messages* 199 Fundamental
* *partial-output-umc.v: 31 Fundamental
%* *breakpoints of umc.v: 31 Breakpoints
Nick> Then I can't really understand why gdb-ui would take so much longer
Nick> than GDB on its own. The overheads are due to the GDB commands
Nick> which are run behind the users back, and the time to update the
Nick> contents of the associated buffers. I would have thought that the
Nick> number of threads should make no difference to the time *difference*
Nick> between the two, unless the threads buffer was present.
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.
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: [EMAIL PROTECTED] |
------------------------------------------
---
Noncombatant, n.: A dead Quaker. -- Ambrose Bierce
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
