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 67325385DC33; Thu,  3 Jun 2021 21:19:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 67325385DC33
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26819] RISC-V: internal-error: int
 finish_step_over(execution_control_state*): Assertion
Date: Thu, 03 Jun 2021 21:19:02 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew.burgess at embecosm dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: andrew.burgess at embecosm dot com
X-Bugzilla-Target-Milestone: 11.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26819-4717-7vF7bLSLUm@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26819-4717@http.sourceware.org/bugzilla/>
References: <bug-26819-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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2021 21:19:02 -0000

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

--- Comment #39 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
At the point where we run into the assertion the vCont/stop-reply packets l=
ook=20
like:

  ...
  Sending packet: $vCont;s:2;c#c2
  Packet received: T05
  Sending packet: $vCont;s:1;c#c1
  Packet received: T05thread:2;
  Sending packet: $vCont;s:2;c#c2
  Packet received: T05
  Sending packet: $vCont;s:1;c#c1
  Packet received: T05thread:2;
  Sending packet: $vCont;s:2;c#c2
  Packet received: T05
  Sending packet: $vCont;s:1#23
  Packet received: T05thread:2

Notice all of the 'vCont;s:2;c' packets get a 'T05' reply.  In each of these
cases it is almost certain that thread-2 was the one that stopped (after the
single step), but in each case GDB will have guessed thread-1.

But things really go wrong when with the last packet we send 'vCont;s:1', b=
ut
get back the reply 'T05thread:2' - a thread that shouldn't be running repor=
ts a
stop!

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