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

[Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>]

> From: Pedro Alves <pedro@palves.net>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 16 Jun 2021 11:01:52 +0100
> 
> So maybe the right thing to do is not the avoid the work "interrupt" altogether
> which seems impossible, but to clarify better what it means in the
> new "Interrupting" node.
> 
> For example, I had:
> 
>   @menu
>   * Breakpoints::                 Breakpoints, watchpoints, and catchpoints
>   * Continuing and Stepping::     Resuming execution
>  +* Interrupting::                Interrupting execution
>   * Skipping Over Functions and Files::
>                                   Skipping over functions and files
>   * Signals::                     Signals
>  @@ -6376,6 +6442,45 @@ default is @code{on}.
>   
>   @end table
>   
>  +@node Interrupting
>  +@section Interrupting
>  +
>  +You can stop the program while it is running in the foreground by
>  +pressing the interrupt character (often @kbd{Ctrl-c}).  If the program
>  +is executing in the background (@pxref{Background Execution}), you can
>  +use the @code{interrupt} command (@pxref{interrupt}).
> 
> (note how the "interrupt" command appears here)

We could try that, although I consider it a less useful change.  The
most confusing wording is when you use "interrupt" in this meaning
anywhere near SIGINT, so that's definitely something to be avoided.