Hi,

I've just started using gdb at my new job, and I'm having a small issue debugging C++ with it. After I execute "continue" or "run" through gdb, I'm not able to return control to gdb.

Based on the documentation I read, I should be able to use Control-C to interrupt the program, and have control return to gdb.

This does not work on my setup. Not sure if it's related, but I'm debugging on a remote machine. I tried through PuTTY and xterm using Exceed XServer. In both cases, gdb does not respond to Control-C.

This is quite annoying because I have to restart my program every time I want to set a breakpoint. Any help would be appreciated.

Thanks!

To see if it's a problem with the terminal settings: Can you do this:

-start gdb
-run your program
-in another terminal window, use: kill -TERM pid (where pid is the process id of the program you're debugging).

This *should* result in GDB regaining control. If it does, then that means that the terminal isn't properly issuing a signal in response to control-c. If it doesn't then it means gdb isn't intercepting the interrupt signal.

Thanks... Actually, I just created a simple C++ program that goes into an infinite loop. I'm able to pause this program in debug mode. I guess the issue is caused by how my program is handling signals.