From: Doug Evans <xdje42@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Need to block SIGCHLD in libgc and guile internal threads
Date: Tue, 26 Aug 2014 01:14:46 -0700 [thread overview]
Message-ID: <CAP9bCMTCpRbQ2=frarOPHSghMUr4fbz=vFCuGjgN=JO9_3eG1g@mail.gmail.com> (raw)
Hi.
I think(!) I understand why gdb is hanging when used with libgc 7.4.x.
This is gdb bug 17247.
https://sourceware.org/bugzilla/show_bug.cgi?id=17247#c30
First, libgc 7.4.x was the first release to default PARALLEL_MARK to
on, so I'm guessing the same "bug" exists in 7.2, it's just not
visible unless one builds libgc with --enable-parallel-mark.
gdb/linux-nat.c calls sigsuspend when the inferior is running and gdb
needs to wait for it to stop.
gdb is waiting on a SIGCHLD at this point.
However, if the SIGCHLD goes to a different thread, say the guile
finalizer thread or a libgc marker thread then the sigsuspend that gdb
calls doesn't wake up and gdb is hung.
So question: Any suggestions for how to approach this?
Here's the hack that I applied to Guile to see if this removes the gdb hang.
I'm not suggesting checking this in. It's just data to help advance
the discussion.
I think there's a general issue here that these threads should block
every signal
they're not expecting, or at least provide a hook to let the app
specify which signals
to block. gdb's need to use SIGCHLD is just one example of a general problem.
diff --git a/libguile/finalizers.c b/libguile/finalizers.c
index 82f292c..95a022c 100644
--- a/libguile/finalizers.c
+++ b/libguile/finalizers.c
@@ -239,6 +239,12 @@ finalization_thread_proc (void *unused)
static void*
run_finalization_thread (void *arg)
{
+ {
+ sigset_t blocked_mask;
+ sigemptyset (&blocked_mask);
+ sigaddset (&blocked_mask, SIGCHLD);
+ sigprocmask (SIG_BLOCK, &blocked_mask, NULL);
+ }
return scm_with_guile (finalization_thread_proc, arg);
}
next reply other threads:[~2014-08-26 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 8:14 Doug Evans [this message]
2014-08-26 16:41 ` Need to block SIGCHLD in libgc and guile internal threads Doug Evans
2014-08-29 17:36 ` mhw
2014-08-30 17:40 ` Doug Evans
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='CAP9bCMTCpRbQ2=frarOPHSghMUr4fbz=vFCuGjgN=JO9_3eG1g@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=guile-devel@gnu.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).