ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:84416] Re: [Ruby trunk Misc#14222] Mutex.lock is not safe inside signal handler: what is?
Date: Sat, 23 Dec 2017 08:03:30 +0000	[thread overview]
Message-ID: <20171223080330.GA7762@whir> (raw)
In-Reply-To: <redmine.journal-68606.20171223074306.103f16c1f330f614@ruby-lang.org>

nobu@ruby-lang.org wrote:
> `Thread.handle_interrupt` doesn't work.

Oops, the main thread may already have a Mutex locked, right?

> You can use `Queue` inside trap context.

Since 2.1 when Queue was reimplemented in C.  Old (pure-Ruby)
Queue used Mutex, but I guess those versions are no longer
supported (and I still have old crap on 1.9.3 :<)

  reply	other threads:[~2017-12-23  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-14222.20171222130013@ruby-lang.org>
2017-12-22 13:00 ` [ruby-core:84404] [Ruby trunk Misc#14222] Mutex.lock is not safe inside signal handler: what is? hkmaly
2017-12-23  1:07   ` [ruby-core:84410] " Eric Wong
2017-12-22 13:11 ` [ruby-core:84406] " hkmaly
2017-12-23  7:43 ` [ruby-core:84415] " nobu
2017-12-23  8:03   ` Eric Wong [this message]
2017-12-25 22:41 ` [ruby-core:84446] " shatrov
2017-12-25 23:37   ` [ruby-core:84448] " Eric Wong
2017-12-27 19:07 ` [ruby-core:84524] " eregontp
2017-12-27 19:58   ` [ruby-core:84526] " Eric Wong
2018-01-25 10:00 ` [ruby-core:85107] " eregontp
2018-01-27  9:39   ` [ruby-core:85155] " Eric Wong
2018-01-28 21:58     ` [ruby-core:85196] " Eric Wong

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-list from there: mbox

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

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

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

  git send-email \
    --in-reply-to=20171223080330.GA7762@whir \
    --to=ruby-core@ruby-lang.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).