From: Mark H Weaver <mhw@netris.org>
To: "Göran Weinholt" <goran@weinholt.se>
Cc: 32367@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Derek Upham" <sand@blarg.net>
Subject: bug#32367: 2.2.4 hangs when a script uses a module that calls sigaction
Date: Tue, 21 Aug 2018 17:30:41 -0400 [thread overview]
Message-ID: <8760032yri.fsf@netris.org> (raw)
In-Reply-To: <877el36crs.fsf@teapot.weinholt.se> ("Göran Weinholt"'s message of "Mon, 06 Aug 2018 11:54:31 +0200")
I don't have time now for a proper investigation, but this might be
related to commit 761cf0fb8c364e885e4c6fced34563f8157c3b84 (Make module
autoloading thread-safe).
Mark
next prev parent reply other threads:[~2018-08-21 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 0:47 bug#32367: 2.2.4 hangs when a script uses a module that calls sigaction Derek Upham
2018-08-06 9:54 ` Göran Weinholt
2018-08-21 21:30 ` Mark H Weaver [this message]
2018-08-22 13:47 ` Derek Upham
2018-08-23 2:20 ` Mark H Weaver
2018-10-21 18:47 ` Mark H Weaver
2018-10-27 14:16 ` Derek Upham
2018-12-15 16:46 ` bug#32367: sigaction hangs Matt Wette
2018-12-15 16:58 ` Matt Wette
2018-12-15 17:50 ` Mark H Weaver
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760032yri.fsf@netris.org \
--to=mhw@netris.org \
--cc=32367@debbugs.gnu.org \
--cc=goran@weinholt.se \
--cc=ludo@gnu.org \
--cc=sand@blarg.net \
/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).