Re: [PATCH 00/17] Interrupting programs that block/ignore SIGINT

[John Baldwin <jhb@FreeBSD.org>]

On 6/15/21 9:18 AM, Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org
>> From: John Baldwin <jhb@FreeBSD.org>
>> Date: Tue, 15 Jun 2021 08:50:18 -0700
>>
>> Put another way, every time I hit Ctrl-C when running a program under
>> GDB, the thought in my mind is not "I want to kill the program", it is
>> "I want to stop the program so I can examine its state in the debugger".
> 
> So, in your opinion, Ctrl-C in this context is different from C-z and
> C-\, to name other keystrokes that cause signals to be delivered?

Yes, due to the "supervisor" role of Ctrl-C and the fact I'm using it as
a GDB action.  FreeBSD has Ctrl-T (for SIGINFO) and I still view that
as an action on the inferior not a request to GDB, but Ctrl-C when
running under GDB is always in my mind "please ask GDB to stop the
program so I can inspect it", not "kill the program".  The fact that
the default is to not pass SIGINT seems consistent with this view since
doing a 'c' after the Ctrl-C resumes it rather than killing the
inferior.  One has to explicitly use 'kill' or 'signal' after a Ctrl-C
to interrupt the child process (vs just stop it).

I do think it probably is clearer to use "stop" instead of "interrupt"
as you noted though since the "interrupted" term is a bit overloaded
and thus ambiguous.

-- 
John Baldwin