From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 80973386EC2F; Sun, 6 Jun 2021 14:28:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 80973386EC2F From: "brobecker at gnat 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, 06 Jun 2021 14:28:00 +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: brobecker at gnat 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: cc target_milestone 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, 06 Jun 2021 14:28:00 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26819 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com Target Milestone|11.1 |--- --- Comment #41 from Joel Brobecker --- Thanks very much for the analysis, Andrew. I agree with you that OpenOCD seems to be behavior very strangely (to say t= he least). It would be nice indeed to improve the situation, but I agree again that it's not clear where and under what condition we could decide to throw= the towel. What I'm concerned about is users starting to get some errors in borderline scenarios that have been working OK thanks to the current heuristics. If we change that, we could negatively affect them. Maybe raise= an error when we're getting a stop from a thread that wasn't supposed to run at all, like you highlighted? In any case, I agree also that this is not blocking for the release anymore= , so I'm removing the 11.1 target milestone. --=20 You are receiving this mail because: You are on the CC list for the bug.=