From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id pthhKwnuyWCSCQAAWB0awg (envelope-from ) for ; Wed, 16 Jun 2021 08:26:49 -0400 Received: by simark.ca (Postfix, from userid 112) id A2C091F163; Wed, 16 Jun 2021 08:26:49 -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.6 required=5.0 tests=MAILING_LIST_MULTI, RDNS_DYNAMIC 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 9D43E1E939 for ; Wed, 16 Jun 2021 08:26:48 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5DD44383D834 for ; Wed, 16 Jun 2021 12:26:48 +0000 (GMT) Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) by sourceware.org (Postfix) with ESMTPS id B3EA1385E823 for ; Wed, 16 Jun 2021 12:26:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B3EA1385E823 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f47.google.com with SMTP id l9so1171122wms.1 for ; Wed, 16 Jun 2021 05:26:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FyFWN0y9i+0YSD6NbzrYBbfn1aC76Ijf+ZsGm8b3y14=; b=AcxLTMWg2wLZZUZ8y1EwDHprjlfxdkhFOiY0uban6zSc7KOte83VU+/A4ZFN253Rpl VnERVirBYmIXxeqiZNcmbOpOMpFTQZb+hhGsM41CPrVthcSuy/yeS7mtHTpXR3a1fsb2 SscgQZbhcI6TukCLYkmibye8snKqLfnBG+1afibVDtdIPKpZhhUOdIILtDs1zH2qfxDq Cy1hOyVW930w8PURrnNl3OTUNtsABMEpXDDqBWFWTDXveQJfrGCJcGEE6Tud7SQLxKIt 6cnmGVhOZ4mvlrV0kN53QTwSKVGC3oWMSU5ROkUTrQxkDQ4Q0K7MoZSc31Tgt1V2LPPo DA1g== X-Gm-Message-State: AOAM532Pomuj2ED/hcr7cr5/JIOHkLr5o6clHy+qtLLB+qHPZQHLKjhG v/s4/5CDHnGCParyfn5UZ5AkrZ6VNRENTg== X-Google-Smtp-Source: ABdhPJxPJh/B5G7uQLThPCrVMLGkeN0MQPdkcdWPOHpy9Byz2MRKC7LM6thW9gO1lsH6X54s03HVsQ== X-Received: by 2002:a7b:c147:: with SMTP id z7mr2836101wmi.135.1623846395196; Wed, 16 Jun 2021 05:26:35 -0700 (PDT) Received: from ?IPv6:2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3? ([2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3]) by smtp.gmail.com with ESMTPSA id h15sm1877465wrq.88.2021.06.16.05.26.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 16 Jun 2021 05:26:34 -0700 (PDT) Subject: Re: [PATCH v2 16/16] Document pseudo-terminal and interrupting changes From: Pedro Alves To: Eli Zaretskii References: <20210614212410.1612666-1-pedro@palves.net> <20210614212410.1612666-17-pedro@palves.net> <83r1h34771.fsf@gnu.org> <86b228b3-31d1-103e-5c98-18a8a6032f2f@palves.net> <83a6nq2eg8.fsf@gnu.org> Message-ID: <15dd75a0-6f41-6bfd-75cf-fd98d7a4a30f@palves.net> Date: Wed, 16 Jun 2021 13:26:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <83a6nq2eg8.fsf@gnu.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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: , Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2021-06-16 1:15 p.m., Eli Zaretskii wrote: >>>> +@value{GDBN} on MS-Windows supports @kbd{C-@key{BREAK}} as an >>>> +alternative interrupt key sequence. @xref{interrupt debuggee on >>>> +MS-Windows}. >>> I'm not sure I understand the significance of this note: after all, a >>> Windows program can install a Ctrl-BREAK handler exactly like it does >>> with Ctrl-C. Is this only about SetConsoleMode? >> I was creating a new "Interrupting" node in the manual, so I thought it >> was a good place to put cross references to other places in the manual >> that talk about interruption. That's all this is. Just like the >> reference to the remote debug section. > My point was more general: why are we taking such a great care > publishing the Ctrl-BREAK support? What's the big deal? > The text that I was xrefing reads: @cindex Ctrl-BREAK, MS-Windows @cindex interrupt debuggee on MS-Windows @anchor{interrupt debuggee on MS-Windows} MS-Windows programs that call @code{SetConsoleMode} to switch off the special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows supports @kbd{C-@key{BREAK}} as an alternative interrupt key sequence, which can be used to interrupt the debuggee even if it ignores @kbd{C-c}. And the sentence I wrote was just my attempt to summarize this information so that the xref made any sense. How would you go about this? - Say something different in the xref? What? - Remove the xref completely? - Move the whole text to the new Interrupt section (removing it from its original place)? Thanks, Pedro Alves