From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 242F63858D37 for ; Wed, 17 Aug 2022 11:07:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 242F63858D37 Received: from fencepost.gnu.org ([2001:470:142:3::e]:43430) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOGtV-0006EU-4z; Wed, 17 Aug 2022 07:07:30 -0400 Received: from [87.69.77.57] (port=2316 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 1oOGtT-0008WJ-5w; Wed, 17 Aug 2022 07:07:28 -0400 Date: Wed, 17 Aug 2022 14:07:17 +0300 Message-Id: <83ilmrdt7e.fsf@gnu.org> From: Eli Zaretskii To: Andrew Burgess Cc: gdb-patches@sourceware.org In-Reply-To: <20220816171822.3315660-1-aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Tue, 16 Aug 2022 18:18:22 +0100) Subject: Re: [PATCH] gdb: new 'maint print frame-id' command References: <20220816171822.3315660-1-aburgess@redhat.com> X-Spam-Status: No, score=1.9 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.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) 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, 17 Aug 2022 11:07:35 -0000 > Date: Tue, 16 Aug 2022 18:18:22 +0100 > From: Andrew Burgess via Gdb-patches > Cc: Andrew Burgess > > When debugging a certain class of GDB bug, I often end up wanting to > know what GDB thinks the frame-id is in a particular frame. It's > not too hard to pull this from some debug output, but I thought it > might be nice if there was a maintenance command that could tell us. > > This commit adds 'maint print frame-id' which prints the frame-id of > the currently selected frame. You can also pass a frame level number > to find the frame-id for a specific frame. > > There's a new test too. > --- > gdb/NEWS | 4 ++ > gdb/doc/gdb.texinfo | 17 +++++ > gdb/frame.c | 28 ++++++++ > gdb/testsuite/gdb.base/maint-print-frame-id.c | 40 +++++++++++ > .../gdb.base/maint-print-frame-id.exp | 68 +++++++++++++++++++ > 5 files changed, 157 insertions(+) > create mode 100644 gdb/testsuite/gdb.base/maint-print-frame-id.c > create mode 100644 gdb/testsuite/gdb.base/maint-print-frame-id.exp Thanks, the documentation parts are OK.