public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-11581-4717-Xzt9Dudx4o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11581-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
In https://sourceware.org/bugzilla/show_bug.cgi?id=11580#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.

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

       reply	other threads:[~2022-11-29 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11581-4717@http.sourceware.org/bugzilla/>
2022-11-29 18:54 ` tromey at sourceware dot org [this message]
2010-05-07 18:49 [Bug threads/11581] New: " k04jg02 at gmail dot com
2010-05-07 18:53 ` [Bug threads/11581] " k04jg02 at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11581-4717-Xzt9Dudx4o@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).