Re: M-x gdb with large files

[Klaus Zeitler]

>>>>> "Nick" == Nick Roberts <address@hidden> 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, i.e. under Solaris
that is 260 lightweight processes. Maybe this (besides the image/core size)
causes problems.


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*):

--- snip ---
Configuring gdb-ui
error in process filter: apply: Args out of range: "(gdb) 
prompt
", 0, 68
error in process filter: Args out of range: "(gdb) 
prompt
", 0, 68
error in process filter: gdb-prompt: Phase error in gdb-prompt (got pre-emacs)
error in process filter: Phase error in gdb-prompt (got pre-emacs)
--- snip ---

I could trace this down to the following lines in my .emacs file:
(eval-after-load "gdb-ui"
    '(progn
       (message "Configuring gdb-ui")
       ;(setq gdb-show-main t)
       ;(setq gdb-many-windows t)
       ;(setq gdb-use-separate-io-buffer t)
       ))

When I remove the eval-after-load, it works.

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             address@hidden  |
 ------------------------------------------
---
I have discovered the art of deceiving diplomats. I tell them
the truth and they never believe me.     -- Camillo Di Cavour