From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 842953861830; Sat, 16 Jan 2021 11:00:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 842953861830 From: "jmatyas at codasip dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/26819] RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion Date: Sat, 16 Jan 2021 11:00:46 +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: jmatyas at codasip 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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: Sat, 16 Jan 2021 11:00:46 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26819 Jan Matyas changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #13 from Jan Matyas --- Hello, I have finally managed to re-test the updated code. I am sorry to report ba= ck that the issue appears not yet fully resolved. Re-running the GDB test scenarios in which this issue was originally encountered (that is: https://github.com/riscv/riscv-tests/tree/master/debug) now triggers a different assert.=20 (1) In many of the above test scenarios, it is the following assert that gets triggered immediately after connecting GDB to the remote server, i.e. OpenO= CD.=20 OpenOCD is at that point already connected to the underlying target, which = is the Spike RISC-V ISA simulator: (gdb) target extended-remote localhost:44553 Remote debugging using localhost:44553 warning: No executable has been specified and target does not support determining executable automatically. Try using the "file" command. ../../../binutils-gdb/gdb/remote.c:7820: internal-error: ptid_t remote_target::select_thread_for_ambiguous_stop_reply(const target_waitstatus*): Assertion `first_resumed_thread !=3D nullptr' failed. A full log from one such test run is attached - 20210116-101128-spike32-CheckMisa.log. It shows the steps to reproduce the issue - most importantly the cmdline arguments to start Spike and OpenOCD. (2) There was one test run in which the original assert was encountered: ../../../binutils-gdb/gdb/infrun.c:5614: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. It is recorded in file: 20210116-101308-spike32_2-ProgramSwWatchpoint.log The revisions of Spike ISA sim, OpenOCD and gdb-binutils that I used were in all cases the latest HEADs as of now: - binutils-gdb: 68b007788a (Fri Jan 15 18:07:07 2021 -0800) - Spike: 35d50bc (Thu Jan 14 09:43:04 2021 -0800) - OpenOCD: ed37337b0 Please let me know if any further information is needed for reproduction or= if you'd like me to re-test any other scenario. Best regards, Jan --=20 You are receiving this mail because: You are on the CC list for the bug.=