From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id WSZrCkbqyWAkCQAAWB0awg (envelope-from ) for ; Wed, 16 Jun 2021 08:10:46 -0400 Received: by simark.ca (Postfix, from userid 112) id 188FA1F163; Wed, 16 Jun 2021 08:10:46 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id DD2441E939 for ; Wed, 16 Jun 2021 08:10:44 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 76C4B38515F9 for ; Wed, 16 Jun 2021 12:10:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76C4B38515F9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1623845444; bh=nFWLkG1rT49zHloawadd1NK0mSJh6I/S6WQuzBdpO2s=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=XmXIBF21XQI4iT6JMrrCTQkRc7Ry0HDFrbCb44KuWzAQG59HW0aP57Oty7Rb1F7Ot GHYcWsWMs0fxdGwC0x9i9K7mvMWpIr98sq83ERcU7o/Q8m3a3sCiYP4m2mutfWs8vO 30U19CvLGzL0oaIQ6cmwy3xQzTK5XIXXHnjdk9MY= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 28EF03858004 for ; Wed, 16 Jun 2021 12:10:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 28EF03858004 Received: from fencepost.gnu.org ([2001:470:142:3::e]:38480) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ltUND-0007Iw-5G; Wed, 16 Jun 2021 08:10:23 -0400 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3988 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ltUNC-00056X-8L; Wed, 16 Jun 2021 08:10:22 -0400 Date: Wed, 16 Jun 2021 15:10:23 +0300 Message-Id: <83bl862eog.fsf@gnu.org> To: Pedro Alves In-Reply-To: (message from Pedro Alves on Wed, 16 Jun 2021 11:01:52 +0100) Subject: Re: [PATCH 00/17] Interrupting programs that block/ignore SIGINT References: <20210603190243.2609886-1-pedro@palves.net> <835yyuwwuu.fsf@gnu.org> <2af9e861-69f2-80c5-606b-2936b6d2d212@palves.net> <83tulz48yr.fsf@gnu.org> <83bl873xuu.fsf@gnu.org> <9c6bbbcc-82db-e487-a8cb-b6ca0a0c4268@FreeBSD.org> X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > From: Pedro Alves > 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.