From: Luis Machado via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <blarsen@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Wondering if record save should be deprecated
Date: Tue, 16 Jul 2024 13:24:26 +0100 [thread overview]
Message-ID: <f29497c4-0f76-4ebe-9657-c4c7b1c9c08b@arm.com> (raw)
In-Reply-To: <3efbc686-a7ec-4699-85ba-b96ea4ec2bad@redhat.com>
On 7/10/24 20:58, Guinevere Larsen via Gdb wrote:
> Hi everyone!
>
> I decided to try a bit of a different workflow for reverse debugging and noticed that using "record save", then loading that file in a new gdb session, and I noticed this generated an assert. The assert itself is not too hard to solve (Hannes had a patch ready when I mentioned it in IRC), but it had me wondering: this bug is present since GDB 10, and there are no bugs in bugzilla about it.
>
> In fact, searching for "record save" only has a stack overflow question from 2.5 years ago that uses precsave, but is about a separate topic. Everything else, including the few reverse debugging tutorials I've seen, never mention this option.
>
> Does it make sense for us to continue supporting this feature that was nigh unusable for 5 releases without anyone noticing? Does anyone reading this makes use of this feature and managed to somehow avoid that crash?
>
If it is easy enough to fix, sounds like that is the way then. As for whether people are using this,
it is hard to tell. I've been hearing more and more about people using RR for their
reverse debugging needs. Does it also save state?
next prev parent reply other threads:[~2024-07-16 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 19:58 Guinevere Larsen via Gdb
2024-07-11 16:52 ` Keith Seitz via Gdb
2024-07-16 12:24 ` Luis Machado via Gdb [this message]
2024-07-16 13:27 ` Guinevere Larsen via Gdb
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=f29497c4-0f76-4ebe-9657-c4c7b1c9c08b@arm.com \
--to=gdb@sourceware.org \
--cc=blarsen@redhat.com \
--cc=luis.machado@arm.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