How do you stop a runaway GDB command?

Question

Occasionally I find myself accidentally triggering a GDB command that takes a long time to complete. An example would be setting a breakpoint using tab-completion on the symbol name. Hitting tab an extra time or two can sometimes trigger GDB listing ALL loaded symbols. Then I have to wait for a few minutes while that completes. Is there a way to interrupt the GDB command other than just killing the whole debugging session?

Possible duplicate of [http://stackoverflow.com/q/597777/72178](http://stackoverflow.com/q/597777/72178) — ks1322, Oct 26 '11 at 19:08

score 0 · Accepted Answer · answered Oct 26 '11 at 18:43

0

Hitting CTRL-C in gdb should interrupt the last (time consuming) command issued. See this article on Debugging with gdb for more info.

answered Oct 26 '11 at 18:43

Michael Goldshteyn

71,784
24
131
181

2

GDB is *supposed* to stop on Ctrl-C, but there are bugs. http://www.cygwin.com/ml/gdb-patches/2011-07/msg00331.html – Employed Russian Oct 26 '11 at 19:59
1

Yeah, it sounds like listing ALL symbols is one of these edge cases where GDB is not responsive. – Skeets Oct 26 '11 at 20:35

How do you stop a runaway GDB command?

1 Answers1