Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: new 'maint print frame-id' command
Date: Wed, 17 Aug 2022 14:07:17 +0300	[thread overview]
Message-ID: <83ilmrdt7e.fsf@gnu.org> (raw)
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)

> Date: Tue, 16 Aug 2022 18:18:22 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Andrew Burgess <aburgess@redhat.com>
> 
> 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.

  parent reply	other threads:[~2022-08-17 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:18 Andrew Burgess via Gdb-patches
2022-08-17  9:21 ` Bruno Larsen via Gdb-patches
2022-08-17 13:20   ` Andrew Burgess via Gdb-patches
2022-08-17 11:07 ` Eli Zaretskii via Gdb-patches [this message]
2022-08-17 14:11 ` Luis Machado via Gdb-patches
2022-08-24 13:45 ` Andrew Burgess via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ilmrdt7e.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox