public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Guinevere Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: kevinb@redhat.com, Guinevere Larsen <blarsen@redhat.com>
Subject: [PATCH v2 0/2] Improving frame printing with recursive
Date: Sun, 24 Sep 2023 14:58:54 +0200	[thread overview]
Message-ID: <20230924125855.983839-2-blarsen@redhat.com> (raw)
In-Reply-To: <20230923103457.29768-2-blarsen@redhat.com>

This started with the first patch, just fixing PR record/29178. However,
Kevin pointed out that I could reuse some of the local variables to make
the function as a whole simpler, which I did on patch 2.

Guinevere Larsen (2):
  gdb/record: print frame information when exiting a recursive call
  gdb/infrun: simplify process_event_stop_test

 gdb/infrun.c                            | 36 ++++++++++++------
 gdb/testsuite/gdb.reverse/recursion.c   | 44 ++++++++++++++++++++++
 gdb/testsuite/gdb.reverse/recursion.exp | 49 +++++++++++++++++++++++++
 3 files changed, 117 insertions(+), 12 deletions(-)
 create mode 100644 gdb/testsuite/gdb.reverse/recursion.c
 create mode 100644 gdb/testsuite/gdb.reverse/recursion.exp

-- 
2.41.0


  parent reply	other threads:[~2023-09-24 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 10:34 [PATCH] gdb/record: print frame information when exiting a recursive call Guinevere Larsen
2023-09-23 21:56 ` Kevin Buettner
2023-09-24  9:55   ` Guinevere Larsen
2023-09-24 12:58 ` Guinevere Larsen [this message]
2023-09-24 12:58 ` [PATCH v2 1/2] " Guinevere Larsen
2023-09-24 17:53   ` Kevin Buettner
2023-09-24 12:58 ` [PATCH v2 2/2] gdb/infrun: simplify process_event_stop_test Guinevere Larsen

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=20230924125855.983839-2-blarsen@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).