Re: gud-tooltip-mode: gdb-prompt: Wrong number of arguments

[Klaus Zeitler]

>>>>> "Klaus" == Klaus Zeitler <address@hidden> writes:
    Klaus> 
    Klaus> emacs backtrace shows:
    Klaus> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
    Klaus>   get-buffer-window(nil)
    Klaus>   gdb-display-source-buffer(#<buffer aMOEthernetPort.cpp>)
    Klaus>   
gud-display-line("/vobs/ubtssw_oam/NodeBMOs/auto_rt/rt/src/aMOEthernetPort.cpp" 
414)
    Klaus>   gud-display-frame()
    Klaus>   gud-filter(#<process gud-umc.vx> "0xb2fc5c8) at 
/vobs/ubtssw_oam/NodeBMOs/auto_rt/rt/src/aMOEthernetPort.cpp:414\n\nsource 
/vobs/ubtssw_oam/NodeBMOs/auto_rt/rt/src/aMOEthernetPort.cpp:414:13146:beg:0x62ebe8\n\npre-prompt\n(gdb)
 \nprompt\n")

When I checked with edebug, the variable gud-last-last-frame in
gdb-display-source-buffer was set to:
"source /vobs/ubtssw_oam/NodeBMOs/auto_rt/rt/src/aMOEthernetPort.cpp"
Maybe the error is caused by that "source" ahead of the filename.

An interactive call: (gud-find-file "source /vobs/.../aMOEthernetPort.cpp")
gave me: "Gud internal error"
Whereas (gud-find-file "source /vobs/.../aMOEthernetPort.cpp") returned:
#<buffer aMOEthernetPort.cpp>

HTH

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             address@hidden  |
 ------------------------------------------
---
I didn't know it was impossible when I did it.