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?
Occasionally I find myself accidentally triggering a GDB command that takes a long time
Share
Hitting CTRL–C in gdb should interrupt the last (time consuming) command issued. See this article on Debugging with gdb for more info.