Hacker News Reader

(To quote myself from LWN) My personal experience with a possibly-related bug: when debugging programs which handle Ctrl+C themselves (like PipeWire and Audacious), pressing Ctrl+C will trigger the app's graceful shutdown process (terminating execution) rather than breaking into the debugger like I want. Is this the same bug, and will the changes to gdb fix this issue?

View on HN

From the article:

As is often the case, Emacs users present their own special challenges. Emacs uses control-C for its own purposes, and remaps SIGINT to control-G instead. In cases like this, the user almost certainly wants control-C to be passed through to the target. The answer is a GDB command that allows the user to specify which key should interrupt the process and return to the GDB prompt.

I find the expectation that ^C puts me back into the debugging session with the target still alive a bit weird. I'd expect the target to handle it the normal way. If I wanted to temporarily halt the target, I'd use ^Z.

Changes nothing for the bug, of course, since the target could be blocking SIGTSTOP.

SIGSTOP can not be blocked.

PS. ^Z sends SIGTSTP not SIGSTOP.

My bad, there's no O in SIGTSTP.

Reply on news.ycombinator.com