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 C0E8D3858C39; Fri, 29 Oct 2021 09:22:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C0E8D3858C39
From: "nyanpasu64 at tuta dot io" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28275] commit_resumed_state assertion failure when killing
 running inferior and running again
Date: Fri, 29 Oct 2021 09:22:31 +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: nyanpasu64 at tuta dot io
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: cc
Message-ID: <bug-28275-4717-IS2Q0TtuIf@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28275-4717@http.sourceware.org/bugzilla/>
References: <bug-28275-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: Fri, 29 Oct 2021 09:22:31 -0000

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

nyanpasu64 at tuta dot io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nyanpasu64 at tuta dot io

--- Comment #2 from nyanpasu64 at tuta dot io ---
I found another procedure to reach the same crash:

- Run a multithreaded GUI app (eg. gdb kwrite).
- Start the application (type run).
- In another terminal, call `killall kwrite` or similar. GDB will say "Thre=
ad 1
"kwrite" received signal SIGTERM, Terminated."
- Type continue into gdb. gdb will say [Thread ... (LWP ...) exited], but n=
ot
[Inferior 1 (process ...) exited ...], even though the PID no longer exists=
 in
/proc/NUMBER.
- Type kill. When gdb asks "Kill the program being debugged? (y or n)", say=
 y.
gdb will say [Inferior 1 (process ...) killed].
- Type run.

This results in the same error: target.c:2603: internal-error: ptid_t
target_wait(ptid_t, target_waitstatus*, target_wait_flags): Assertion
`!proc_target->commit_resumed_state' failed.

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