From: Guinevere Larsen via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 0/2] Improving frame printing with recursive
Date: Wed, 27 Sep 2023 12:19:50 +0200 [thread overview]
Message-ID: <20230927101950.1913970-3-blarsen@redhat.com> (raw)
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.
Changelog for v3:
* Fix remaining style issues in the testsuite
Changelog for v2:
* Added second patch in the series
* Fixed some tyle issues
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 | 45 +++++++++++++++++++++++++
3 files changed, 113 insertions(+), 12 deletions(-)
create mode 100644 gdb/testsuite/gdb.reverse/recursion.c
create mode 100644 gdb/testsuite/gdb.reverse/recursion.exp
--
2.41.0
next reply other threads:[~2023-09-27 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 10:19 Guinevere Larsen via Gdb-patches [this message]
2023-09-27 10:19 ` [PATCH v3 1/2] gdb/record: print frame information when exiting a recursive call Guinevere Larsen via Gdb-patches
2023-09-27 21:26 ` Kevin Buettner via Gdb-patches
2023-09-27 23:22 ` Kevin Buettner via Gdb-patches
2023-09-28 1:57 ` Kevin Buettner via Gdb-patches
2023-10-02 13:11 ` Guinevere Larsen via Gdb-patches
2023-09-27 10:19 ` [PATCH v3 2/2] gdb/infrun: simplify process_event_stop_test Guinevere Larsen 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=20230927101950.1913970-3-blarsen@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=blarsen@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