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*
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
Nick Is it a new problem? i.e. did it work previously?
Yes and yes
Then I think it's due to the recent changes in eval-after-load
not gdb-ui.
I could trace this down to the following lines in my .emacs file:
(eval-after-load gdb-ui
'(progn
(message
Nick Did you do this with gdb-many-windows set to t?
tried it with gdb-many-windows set to t or nil, doesn't seem to make
a difference.
You might need to check that there aren't other buffers present which just
aren't visible.
Nick How deep is your stack?
Only 9 frames
Nick == Nick Roberts [EMAIL PROTECTED] writes:
Nick
Nick Did you do this with gdb-many-windows set to t?
tried it with gdb-many-windows set to t or nil, doesn't seem to make
a difference.
Nick How deep is your stack?
Only 9 frames in this case, but we have about 130 threads,
BTW there must be a new problem with the newest CVS version. A call like:
M-x gdb - gdb --annotate=3 umc.vx
gives me the following error (taken from *Messages*):
Is it a new problem? i.e. did it work previously?
--- snip ---
Configuring gdb-ui
error in process filter: apply: Args out
I also have serious performance issues with the new gdb interface, e.g.
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.
This is almost certainly not an
