public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brandon.belew at zetier dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/31610] Abort when stepping through a restored recording
Date: Fri, 05 Apr 2024 11:48:03 +0000	[thread overview]
Message-ID: <bug-31610-4717-vJ5MLxfW7X@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31610-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31610

--- Comment #1 from Brandon Belew <brandon.belew at zetier dot com> ---
As a follow-up, even on builds that crash with this assertion, I can still
`record goto INSN` to move through the recording history. I hacked up a rf and
rb command (reverse forward and reverse backward) that looks essentially like 

```
set $_r_inst = 1

define rf
record goto $_r_inst + 1
set $_r_inst = $_r_inst + 1
end 

define rb
record goto $_r_inst - 1
set $_r_inst = $_r_inst -1 
end 
```

And this works as a hacky way to step forwards and backwards through the
restored recording without triggering the crash, but this for instance does not
let me do the equivalent of `continue` or `reverse-continue`.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2024-04-05 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 11:16 [Bug record/31610] New: " brandon.belew at zetier dot com
2024-04-05 11:48 ` brandon.belew at zetier dot com [this message]
2024-04-05 15:16 ` [Bug record/31610] " brandon.belew at zetier dot com
2024-04-06  9:46 ` ssbssa at sourceware dot org

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=bug-31610-4717-vJ5MLxfW7X@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).