From: Eli Zaretskii <eliz@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
Date: Mon, 01 Sep 2014 20:10:40 +0300 [thread overview]
Message-ID: <83vbp7fer3.fsf@gnu.org> (raw)
In-Reply-To: <87r3zv71qy.fsf@gnu.org>
> From: ludo@gnu.org (Ludovic Courtès)
> Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
> Date: Mon, 01 Sep 2014 18:18:45 +0200
>
> Eli Zaretskii <eliz@gnu.org> skribis:
>
> > Perhaps we should request GC and Guile to provide capabilities to
> > disable threads at run time, then.
>
> I don’t think we need to go this far: reading the recent discussions, it
> seems Doug found a way to make sure Guile’s and libgc’s internal threads
> don’t receive signals that GDB is interested in, which should be enough
> for practical purposes.
That's just the tip of an iceberg, I'm afraid.
next prev parent reply other threads:[~2014-09-01 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m31trwv5o1.fsf@sspiff.org>
[not found] ` <834mwsh2nu.fsf@gnu.org>
2014-08-31 20:20 ` [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile Doug Evans
2014-09-01 2:36 ` Eli Zaretskii
2014-09-01 10:11 ` Ludovic Courtès
2014-09-01 14:39 ` Eli Zaretskii
2014-09-01 16:18 ` Ludovic Courtès
2014-09-01 17:10 ` Eli Zaretskii [this message]
2014-09-01 22:04 ` Doug Evans
2014-09-02 15:25 ` Eli Zaretskii
2014-09-05 8:26 ` Doug Evans
2014-09-05 8:48 ` Eli Zaretskii
2014-09-05 10:51 ` Pedro Alves
2014-09-05 11:51 ` Eli Zaretskii
2014-09-05 12:48 ` Pedro Alves
2014-09-05 11:50 ` Ludovic Courtès
2014-09-01 12:48 ` Gary Benson
2014-09-01 16:34 ` 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=83vbp7fer3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).