From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4C3693830B34; Thu, 24 Nov 2022 16:18:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C3693830B34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669306710; bh=iqOOk0D/fG6Q8DkFRe8SCUIxAf/KzgSS8DwRB7YFERo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XUgZeORhjuF0FZQfYTGGGoXWCNthbVnu/5l6PlsWjv6kRTOsaQj1mqtVoR+QBBVgK zZgvm3GFmnOqt8BuH6S+LASv5KM18hp+MjHzt/AhlT2wwSHVxQBjWDGlI5665Te+SV MRX6f1BTKV4LGjlch6stF0h+M23EhVDfwWItfJPw= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging Date: Thu, 24 Nov 2022 16:18:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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.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=3D19471 --- Comment #19 from Tom Tromey --- Created attachment 14473 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14473&action=3Ded= it basic patch This implements the basic functionality. I wasn't super sure about the condition. Checking sched_multi made sense to me, but I wasn't sure if anything special was needed for scheduler locking or non-stop. Like, maybe in non-stop we should skip the restart as well, on the theory that everything the user wants running is already running. I also have the start of "catch exit", but one issue with implementing that is that there's no event_thread in the 'ecs'. So, there's nowhere to put the bpstat. --=20 You are receiving this mail because: You are on the CC list for the bug.=