From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5981C3858012; Sun, 8 Nov 2020 10:07:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5981C3858012 From: "andrew.burgess at embecosm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/26819] RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion Date: Sun, 08 Nov 2020 10:07:23 +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: 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: cc Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2020 10:07:23 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26819 Andrew Burgess changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.burgess at embecosm= dot com --- Comment #1 from Andrew Burgess --- Jan, Thank you for including such clear steps to reproduce, they were very helpf= ul. I tried following the steps but could not reproduce this issue, however, th= anks to your great instructions I was able to see where I diverge from your behaviour. When you start GDB, you report this: (gdb) info threads Id Target Id Frame=20 * 1 Thread 1 (Name: Hart 0, RV64) 0x00000012123408b0 in stack_bottom () 2 Thread 2 (Name: Hart 1, RV64) 0x000000121234089c in stack_bottom () (gdb) thread 2 However, when I start GDB, I see this: (gdb) info threads Id Target Id Frame=20 * 1 Thread 1 (Name: Hart 0, RV64) 0x0000001212340840 in stack_bottom () I did try following the rest of your steps using thread 1, but the bug didn= 't reproduce. The fact that I only see a single thread doesn't seem too surprising given = that in my openocd startup I see this: Warn : `-rtos riscv` is deprecated and will be removed at the end of 2020! Please Warn : change your configuration to use `-rtos hwthread` instead. To do th= at, you Warn : will have to explicitly list every hart in the system as a separate target. See Warn : https://github.com/riscv/riscv-tests/blob/ec6537fc4a527ca88be2f045e01c460e6= 40ab9c5/debug/targets/SiFive/HiFiveUnleashed.cfg#L11 Warn : for an example. And: Info : Examined RISC-V core; found 1 harts Info : hart 0: XLEN=3D64, misa=3D0x8000000000141129 Could you confirm the exact git SHA you are using for spike and openocd ple= ase. Or any other suggestions for what might be different between our environme= nts? --=20 You are receiving this mail because: You are on the CC list for the bug.=