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 94F703858D20; Tue, 29 Nov 2022 18:54:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94F703858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1669748086;
	bh=1cFUQ4x/3h0bJPE4iWrbcy+bpQjo/Mqm3BG2ZsJNOaQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=t0xTlwGq3p+riiEM01x1sIuxRtPGEO8mXZ14iQXCxJFtE6gz6psA6Jdf2IF9W+MEp
	 6jFXjemR9DrBgB1Mh4nGbWuQn4xyzqzhbyOGyc3wyMqyV6rdxQRFzl3XEx2U2FJDZk
	 4uC8ITYhfb1S3sIW8+uyfaJJreHsDpcr6FR96vf0=
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/11581] 'set scheduler-locking on' should be automatic
 in response to SIGABRT and SIGSEGV
Date: Tue, 29 Nov 2022 18:54:45 +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: 7.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at sourceware dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 7.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-11581-4717-Xzt9Dudx4o@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-11581-4717@http.sourceware.org/bugzilla/>
References: <bug-11581-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
List-Id: <gdb-prs.sourceware.org>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot o=
rg

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
In https://sourceware.org/bugzilla/show_bug.cgi?id=3D11580#c3, Pedro
asked for no special casing like this.

It seems to me you could implement it yourself by using
"catch signal".  The commands could disable scheduler-locking.

I agree that some kind of warning when scheduler-locking can't
apply would be good to have.  Maybe it could be done once
per exec target.

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