From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id k/wiH0BJJ2IINAAAWB0awg (envelope-from ) for ; Tue, 08 Mar 2022 07:17:04 -0500 Received: by simark.ca (Postfix, from userid 112) id 6A5EF1F3CA; Tue, 8 Mar 2022 07:17:04 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,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 EB54F1F0D2 for ; Tue, 8 Mar 2022 07:17:03 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5781D385C401 for ; Tue, 8 Mar 2022 12:17:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5781D385C401 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1646741823; bh=/JNSfMQ2S3BX1eK6lIS76WMGijhLzdTx6YwF5zsBNxY=; 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=roRFRb/Ev39D+WKmoThOlb7TyLJyouGJA+rSzy/SkK7Uodib1vdF+EidelG0misbq U0qm5Hz3kjWT318jBE3v4PGuDe4SM2QRmEqHTyLvcx8/MdhKRAzlN4/8IeoKrxMpq7 TRtsl8XAq/ofpstr0hYEEhA/hkOKuTJ69zKAkLqc= Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 62DD03858C83 for ; Tue, 8 Mar 2022 12:16:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 62DD03858C83 Received: from [2001:470:142:3::e] (port=36962 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nRYlf-0005Od-GU; Tue, 08 Mar 2022 07:16:43 -0500 Received: from [87.69.77.57] (port=3604 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 1nRYle-0002bF-TA; Tue, 08 Mar 2022 07:16:43 -0500 Date: Tue, 08 Mar 2022 14:16:36 +0200 Message-Id: <83ee3cfxln.fsf@gnu.org> To: Andrew Burgess In-Reply-To: (message from Andrew Burgess via Gdb-patches on Mon, 7 Mar 2022 22:13:38 +0000) Subject: Re: [PATCHv3 06/15] gdb/tui: add a tui debugging flag References: 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" > Date: Mon, 7 Mar 2022 22:13:38 +0000 > From: Andrew Burgess via Gdb-patches > Cc: Andrew Burgess > > diff --git a/gdb/NEWS b/gdb/NEWS > index 1275d967a2d..eb18ac47804 100644 > --- a/gdb/NEWS > +++ b/gdb/NEWS > @@ -133,6 +133,10 @@ winwidth > the width of a tui window to be adjusted when windows are laid out > in horizontal mode. > > +set debug tui on|off > +show debug tui > + Control the display of debug output about GDB's tui. > + > * Changed commands > > maint packet > diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo > index 6081aa85af4..60173e07747 100644 > --- a/gdb/doc/gdb.texinfo > +++ b/gdb/doc/gdb.texinfo > @@ -29205,6 +29205,17 @@ > source text at the next tab stop; the compact display uses only as > much space as is needed for the line numbers in the current file, and > only a single space to separate the line numbers from the source. > + > +@kindex set debug tui > +@item set debug tui @r{[}on|off@r{]} > +Turn on or off display of @value{GDBN} internal debug messages relating > +to the TUI. > + > +@kindex show debug tui > +@item show debug tui > +Show the current status of displaying @value{GDBN} internal debug > +messages relating to the TUI. > + The documentation parts are OK, but I wonder whether we should mention the caveats you described, at least in NEWS. I'm aware that we don't usually describe known bugs, but since you say this could cause crashes, perhaps it justifies an exception? Thanks.