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 E396D3858C3A; Mon, 10 Jan 2022 14:40:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E396D3858C3A
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/19471] unexpected stop in multi-inferior debugging
Date: Mon, 10 Jan 2022 14:40:36 +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: 
Message-ID: <bug-19471-4717-xlwfcgHhu1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-19471-4717@http.sourceware.org/bugzilla/>
References: <bug-19471-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: Mon, 10 Jan 2022 14:40:37 -0000

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

--- Comment #16 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Mark Wielaard from comment #15)
> (In reply to Tom Tromey from comment #14)
> > I've been thinking about this today and wondering how useful
> > "catch exit" would be.  Seems easy enough to implement but what
> > scenario would I use it in?
>=20
> Sometimes an internal sanity check calls exit when detecting something odd
> going on. It would be useful to catch where/when that happens with catch
> exit.

In the implementation we're discussing, the stop would happen
after the process already exited.  Would that still be useful?
I can see it being useful with the TRACEEXIT implementation since
memory would still be available... but I have trouble picturing
using the infrun implementation.
(Also you can "catch syscall" to catch exits, I think.  Except
signals, but those usually cause stops anyway.)

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