From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id DF3A23858415; Fri,  5 Apr 2024 11:48:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF3A23858415
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1712317683;
	bh=5t0PXF2tVlsVuCP2O8lgwYOknEvgOoxTphdIzCHjm8Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gSRBEIrb2Gny1IQtiG1vb99YsSntKdClVvFJkGY0cG3fEjSVmlO8YS82MOr6fehLt
	 f204wzBxJnYNwLybAW/gT0udQ48TKGiEXABCB6aURUvkzrjeuGZZI3SLhp/vd/zmOe
	 0CHqyttusPf9ednPayogDDB4tiybZuLsD3mSwci4=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: record
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: brandon.belew at zetier dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31610-4717-vJ5MLxfW7X@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31610-4717@http.sourceware.org/bugzilla/>
References: <bug-31610-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

--- 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 li=
ke=20

```
set $_r_inst =3D 1

define rf
record goto $_r_inst + 1
set $_r_inst =3D $_r_inst + 1
end=20

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

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`.

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