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 python/17314] Any thread created by Python must block SIGCHLD
Date: Sun, 12 Jun 2022 16:42:12 +0000	[thread overview]
Message-ID: <bug-17314-4717-SYYPUdOWlo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17314-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

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

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
On Linux, SIGCHLD could probably be handled using signalfd.
I'm not sure if gdb supports older kernels that don't have this, though.

However it seems to me that SIGINT should also be blocked in
new threads.  gdb also blocks SIGALRM and SIGWINCH in its own
worker threads, so maybe those ought to be as well.

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

  parent reply	other threads:[~2022-06-12 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 20:37 [Bug python/17314] New: " dje at google dot com
2014-08-31  2:40 ` [Bug python/17314] " xdje42 at gmail dot com
2014-09-13 22:55 ` cvs-commit at gcc dot gnu.org
2022-06-12 16:42 ` tromey at sourceware dot org [this message]
2023-03-07 18:38 ` tromey at sourceware dot org
2023-07-31 16:03 ` tromey at sourceware dot org

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-17314-4717-SYYPUdOWlo@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).