From: Bruno Larsen <blarsen@redhat.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 1/2] Change calculation of frame_id by amd64 epilogue unwinder
Date: Tue, 25 Oct 2022 15:51:23 +0200 [thread overview]
Message-ID: <ac887498-11c8-287e-f392-9e6ebf3da535@redhat.com> (raw)
In-Reply-To: <c39ef3a9-1fbf-0ded-7959-75cf523c1a8e@simark.ca>
On 25/10/2022 15:44, Simon Marchi wrote:
> On 10/5/22 06:38, Bruno Larsen via Gdb-patches wrote:
>> When GDB is stopped at a ret instruction and no debug information is
>> available for unwinding, GDB defaults to the amd64 epilogue unwinder, to
>> be able to generate a decent backtrace. However, when calculating the
>> frame id, the epilogue unwinder generates information as if the return
>> instruction was the whole frame.
>>
>> This was an issue especially when attempting to reverse debug, as GDB
>> would place a step_resume_breakpoint from the epilogue of a function if
>> we were to attempt to skip that function, and this breakpoint should
>> ideally have the current function's frame_id to avoid other problems
>> such as PR record/16678.
>>
>> This commit changes the frame_id calculation for the amd64 epilogue,
>> so that it is always the same as the dwarf2 unwinder's frame_id.
>>
>> It also adds a test to confirm that the frame_id will be the same,
>> regardless of using the epilogue unwinder or not, thanks to Andrew
>> Burgess.
>>
>> Co-Authored-By: Andrew Burgess <aburgess@redhat.com>
>> ---
>> gdb/amd64-tdep.c | 10 +-
>> .../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 ++++++++++++++++++
>> 4 files changed, 206 insertions(+), 5 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
> Hi Bruno,
>
> On Ubuntu 22.04, I can get this new test to fail quite reliably with:
>
> $ taskset -c 1 make check TESTS="gdb.base/unwind-on-each-insn.exp" RUNTESTFLAGS="--target_board=native-gdbserver"
>
> Can you give it a try?
Hi Simon,
I'll take a look, thanks for bringing this to my attention!
Cheers,
Bruno
>
> Simon
>
next prev parent reply other threads:[~2022-10-25 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 10:38 [PATCH v4 0/2] Fix reverse nexting over recursions Bruno Larsen
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 [this message]
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=ac887498-11c8-287e-f392-9e6ebf3da535@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).