Slickedit times out waiting for response from GDB

[adavies25]

Hello,

I'm trying to attach to a process with GDB and although the debugger starts up it doesn't suspend execution of the program like previous versions. When I try to set a breakpoint slickedit hangs for 15 seconds and eventually comes back with:

Unable to set breakpoint at this location: Timed out waiting for response from GDB

Then when I try and detach from the process it hangs as well and I get:

Error detaching debugger: Error detaching debugger from target process

I've read the following posts:
http://community.slickedit.com/index.php?topic=59.0
http://community.slickedit.com/index.php?topic=105.0

however I wasn't able to fix the problem.

When I startup debugging by attaching to the process I see gdb running in the background as:

/usr/local/bin/gdb -nx -interpreter=mi -quiet

so I know I'm using the right debugger.

I have SE version 12.0.3.0 running on CentOS release 5 (Final) on an Intel Core 2 Duo using GDB 6.7.1 that was built on the same machine. I've also tried GDB version 6.5-16.el5rh for Red Hat and the GDB version 6.6 shipped with slickedit.

When I do Debug -> Debugger Options it also hangs for 10 seconds and then pops up the dialog box. The Info tab is completely blank.

Here is my vs.log with debugging turned on when I set the breakpoint:

_UpdateDebugger: status=-5700 event= flags=0 thread=0 time=7711940081590104 mtime=18:39:50 ELAPSED TIME=0
_UpdateDebugger: polling, time=7711940081590381
selecting session: 1 name=WORKSPACE: /home/adavies/dev/branch1/branch1.vpw
_UpdateDebugger: status=-5700 event= flags=0 thread=0 time=7711940081590381 mtime=18:39:50 ELAPSED TIME=0
GDB send SIGINT
GDB event: time=4990000 &"Quit\n"

GDB send SIGINT
GDB event: time=4990000 &"Quit\n"

======================================
GDB command_reply: time=4990000 command=-data-disassemble -f "/home/adavies/dev/branch1/server/worldd/message.cpp" -l 823 -n 0 -- 1
GDB command_reply: send time=4990000 elapsed=0
GDB event: time=4990000 ^done,asm_insns=[src_and_asm_line={line="819",file="worldd/message.cpp",line_asm_insn=[]}]

GDB event: time=4990000 (gdb)

GDB command_reply: reply=^done,asm_insns=[src_and_asm_line={line="819",file="worldd/message.cpp",line_asm_insn=[]}]


GDB command_reply: reply time=4990000 elapsed=0
GDB command_reply: sending -exec-continue
GDB event: time=4990000 ^running

GDB event: time=4990000 (gdb)

GDB send SIGINT
======================================
GDB command_reply: time=4990000 command=-break-insert worldd/message.cpp:823
GDB command_reply: send time=4990000 elapsed=0
GDB command_reply: time=4990000 status=-5701
GDB command_reply: sending -exec-continue
_UpdateDebugger: polling, time=7711940081698243
selecting session: 1 name=WORKSPACE: /home/adavies/dev/branch1/branch1.vpw
_UpdateDebugger: status=-5700 event= flags=0 thread=0 time=7711940081698243 mtime=18:41:38 ELAPSED TIME=0
_UpdateDebugger: status=-5700 event= flags=0 thread=0 time=7711940081698295 mtime=18:41:38 ELAPSED TIME=52
_UpdateDebugger: status=-5700 event= flags=0 thread=0 time=7711940081698347 mtime=18:41:38 ELAPSED TIME=104

It correctly inserts the breakpoint at message.cpp:line 823 but the breakpoint is disabled and I get that "Timed out waiting for response from GDB" popup message. The places it hangs the most are at the "GDB send SIGINT".

Any help would be greatly appreciated. I love slickedit and have been using it for a long time.

Thanks,
Alan

[Dennis]

Get SlickEdit 2008.  There was a fix in the suspend logic, I would expect it to work better.  Give it a try and let us know.

[adavies25]

I got SlickEdit 2008. However the same problem happens.... however I was able to figure it out and...

Wow. I feel dumb. 

Once the debugger starts, the first thing you have to do is press pause to suspend the debugger first. Trying to set a breakpoint without suspending first makes GDB and SlickEdit get all out of wack as above. Maybe it is obvious to other people to suspend first but then again I might be used to Visual Studio's throw up a breakpoint whenever style.

Yay! Now I can debug.