From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/2] Fix reverse nexting over recursions
Date: Wed, 5 Oct 2022 12:38:31 +0200 [thread overview]
Message-ID: <20221005103832.3163424-1-blarsen@redhat.com> (raw)
This patch series fixes gdb record/16678, GDB being unable to
reverse-next over a recursive function. However, the simple way to fix
it hit a snag when I discovered that the amd64 epilogue unwinder would
give a different frame id than the dwarf2 unwinder would in the rest of
the function. This patch series first change this discrepancy, then
fixes the bug.
Changelog for v4:
* more style fixes, thanks Pedro.
* Reworked part of the test, as it was not detecting failures
correctly.
Changelog for v3:
* fix some comments on the amd64_epilogue_unwinder
* fix style for the step-reverse test
Changelog for v2:
* Implemented Pedro Alves's suggestion to simplify the fix
* Added the first patch to fix a regression that the simple fix
would introduce.
Bruno Larsen (2):
Change calculation of frame_id by amd64 epilogue unwinder
gdb/reverse: Fix stepping over recursive functions
gdb/amd64-tdep.c | 10 +-
gdb/infrun.c | 2 +-
.../gdb.base/unwind-on-each-insn-foo.c | 22 +++
gdb/testsuite/gdb.base/unwind-on-each-insn.c | 25 +++
.../gdb.base/unwind-on-each-insn.exp | 154 ++++++++++++++++++
gdb/testsuite/gdb.reverse/step-precsave.exp | 6 +-
gdb/testsuite/gdb.reverse/step-reverse.c | 19 ++-
gdb/testsuite/gdb.reverse/step-reverse.exp | 55 ++++++-
8 files changed, 280 insertions(+), 13 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/unwind-on-each-insn-foo.c
create mode 100644 gdb/testsuite/gdb.base/unwind-on-each-insn.c
create mode 100644 gdb/testsuite/gdb.base/unwind-on-each-insn.exp
--
2.37.3
next reply other threads:[~2022-10-05 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 10:38 Bruno Larsen [this message]
2022-10-05 10:38 ` [PATCH v4 1/2] Change calculation of frame_id by amd64 epilogue unwinder Bruno Larsen
2022-10-25 13:44 ` Simon Marchi
2022-10-25 13:51 ` Bruno Larsen
2022-10-25 13:59 ` Simon Marchi
2022-10-25 14:13 ` Bruno Larsen
2022-10-25 14:37 ` Simon Marchi
2022-10-05 10:38 ` [PATCH v4 2/2] gdb/reverse: Fix stepping over recursive functions Bruno Larsen
2022-10-25 14:55 ` Simon Marchi
2022-10-25 16:22 ` Tom de Vries
2022-11-02 17:03 ` Bruno Larsen
2022-11-02 17:46 ` Simon Marchi
2022-11-03 9:08 ` [PATCH] gdb/testsuite: add KFAILs to gdb.reverse/step-reverse.exp Bruno Larsen
2022-11-03 13:06 ` Simon Marchi
2022-11-03 14:30 ` [PATCHv2] " Bruno Larsen
2022-11-03 16:59 ` Simon Marchi
2022-11-04 11:06 ` Bruno Larsen
2022-10-20 7:42 ` [PING][PATCH v4 0/2] Fix reverse nexting over recursions Bruno Larsen
2022-10-20 18:56 ` Tom Tromey
2022-10-21 10:50 ` Bruno 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=20221005103832.3163424-1-blarsen@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).