From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 01E5D3858C20 for ; Wed, 9 Mar 2022 12:58:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 01E5D3858C20 Received: from [2001:470:142:3::e] (port=34882 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 1nRvtk-0007wE-Cx; Wed, 09 Mar 2022 07:58:36 -0500 Received: from [87.69.77.57] (port=2980 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 1nRvtj-0004W2-JS; Wed, 09 Mar 2022 07:58:36 -0500 Date: Wed, 09 Mar 2022 14:58:29 +0200 Message-Id: <83wnh3e0zu.fsf@gnu.org> From: Eli Zaretskii To: Andrew Burgess Cc: gdb-patches@sourceware.org In-Reply-To: <87y21juz2g.fsf@redhat.com> (message from Andrew Burgess on Wed, 09 Mar 2022 11:48:07 +0000) Subject: Re: [PATCHv3 06/15] gdb/tui: add a tui debugging flag References: <83ee3cfxln.fsf@gnu.org> <87y21juz2g.fsf@redhat.com> X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.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: , X-List-Received-Date: Wed, 09 Mar 2022 12:58:38 -0000 > From: Andrew Burgess > Cc: gdb-patches@sourceware.org > Date: Wed, 09 Mar 2022 11:48:07 +0000 > > > 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? > > I don't know if that's really a route we want to start going down. Why > would this bug deserve a NEWS entry over any other bug? Because users could crash their GDB session by doing completely innocent and reasonable things? But I see that the crashes are not related to the new setting you are adding, so I withdraw my suggestion to mention the crashes in NEWS.