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 CFE173858C74; Tue,  9 Jan 2024 15:41:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CFE173858C74
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1704814888;
	bh=JhF2UC8mqBS0uRNmCYx7ASdecgh7RNxthwHzqZ+n26A=;
	h=From:To:Subject:Date:From;
	b=wm9iM8ARS8LPvJD0e7u2QUCkP2vRfv4Pc4j5EBfNWRxI4f4pM7TXRFwlrWtxPZski
	 uUuPmiaCp4aisyCQA1yLldWxExArSpXChLjKPbrfKAZ+gZU0y16aAVU0R3eMfdOvhV
	 UcQTkTGaZLKyrsCJl0OjfVrIWzHsap2b0zcec2po=
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/31224] New: Hard to understand warning when reaching end
 of reverse-execution history
Date: Tue, 09 Jan 2024 15:41:28 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
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: blarsen at redhat dot com
X-Bugzilla-Status: NEW
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-31224-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=3D31224

            Bug ID: 31224
           Summary: Hard to understand warning when reaching end of
                    reverse-execution history
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: record
          Assignee: unassigned at sourceware dot org
          Reporter: blarsen at redhat dot com
  Target Milestone: ---

Currently, if a user is running a record session, moves backwards a bit and
moves forward again, they may hit the following warning:

> No more reverse-execution history.

My very scientific testing of asking one end user highlighted that this mes=
sage
sounds like GDB will be unable to move the inferior forward, when all it me=
ans
is that we will make the CPU actually execute the inferior, instead of
simulating it.

This is made worse because when the inferior executes backwards to the end =
of
the history, GDB really can't make the inferior continue backwards and the
message is exactly the same.

It would be nice if the warning was different when moving forward, and was
reworded to make clear that the inferior can continue executing. I would
suggest changing it to:

> No more reverse-execution history. Switching to normal execution

However, I'm open to other ideas.

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