From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CC67F395BC26; Wed, 16 Nov 2022 15:36:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC67F395BC26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668612988; bh=3boBnxZtpchPBGEixAf1NI0uyo9EGuAzjF3sPgGXD/c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xtc7vP6w3U+BL/dzgEe1Aw53oeP1TdMPDBj7C4sFONIocms1djv1EiYCgwq4YxpTO iTk8KNvwxHbtqtwqdx7PEGpoyf7nhPymIe5dj48pTH+4Z2+gmAsAwhMHCIkan+ODte OV0YGa5kyUI4ud33tJq8MJpUPzu3WbWJxmUOjC3s= From: "aburgess at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/28275] commit_resumed_state assertion failure when killing running inferior and running again Date: Wed, 16 Nov 2022 15:36:28 +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: aburgess 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: attachments.isobsolete attachments.created 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D28275 Andrew Burgess changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #13630|0 |1 is obsolete| | --- Comment #10 from Andrew Burgess --- Created attachment 14458 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14458&action=3Ded= it Patch including test and possible fix (for issue in comment #1) I took a look at the issue I raised in comment #1. This updated patch incl= udes a test that I think is now ready for upstream, and a possible fix. I've not posted this to the m/l as I believe Simon is currently looking at wider commit_resumed_state issues, so I don't want to conflict with any work he's doing. Hopefully the new test at least will be included with anything Simon posts upstream, and the fix I propose might be helpful. --=20 You are receiving this mail because: You are on the CC list for the bug.=