From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: wip-threads-and-fork
Date: Sat, 03 Mar 2012 22:20:46 +0100 [thread overview]
Message-ID: <8762el5qkx.fsf@gnu.org> (raw)
In-Reply-To: <87mx7xd4s0.fsf@pobox.com> (Andy Wingo's message of "Sat, 03 Mar 2012 17:32:15 +0100")
Hey!
Andy Wingo <wingo@pobox.com> skribis:
> How do you feel about raising an error if primitive-fork is called, and
> there are other threads running?
I think I’d prefer a solution where libguile-internal threads and locks
are suitably handled upon fork (basically what wip-threads-and-fork
does), and where users are provided with mechanisms to do the same at
their level–which boils down to exposing pthread_atfork.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-03-03 21:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 22:10 wip-threads-and-fork Andy Wingo
2012-02-22 21:40 ` wip-threads-and-fork Andy Wingo
2012-02-23 15:05 ` wip-threads-and-fork Andy Wingo
2012-02-23 15:49 ` wip-threads-and-fork Nala Ginrut
2012-02-23 16:13 ` wip-threads-and-fork Andy Wingo
2012-02-24 3:00 ` wip-threads-and-fork Nala Ginrut
2012-02-24 10:21 ` wip-threads-and-fork Andy Wingo
2012-02-24 14:08 ` wip-threads-and-fork Nala Ginrut
2012-02-24 14:47 ` wip-threads-and-fork Andy Wingo
2012-02-24 15:25 ` wip-threads-and-fork Nala Ginrut
2012-02-26 22:03 ` wip-threads-and-fork Ludovic Courtès
2012-02-27 9:44 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:40 ` wip-threads-and-fork Ludovic Courtès
2012-02-24 18:57 ` wip-threads-and-fork Andy Wingo
2012-02-25 2:21 ` wip-threads-and-fork Nala Ginrut
2012-02-25 2:30 ` wip-threads-and-fork Nala Ginrut
2012-02-25 18:01 ` wip-threads-and-fork Andy Wingo
2012-02-26 2:35 ` wip-threads-and-fork Nala Ginrut
2012-02-26 22:00 ` wip-threads-and-fork Ludovic Courtès
2012-02-27 9:39 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:35 ` wip-threads-and-fork Ludovic Courtès
2012-03-03 16:32 ` wip-threads-and-fork Andy Wingo
2012-03-03 21:20 ` Ludovic Courtès [this message]
2012-03-04 11:38 ` wip-threads-and-fork Andy Wingo
2012-03-21 21:26 ` wip-threads-and-fork Ludovic Courtès
2012-03-22 2:48 ` wip-threads-and-fork Nala Ginrut
2012-03-23 9:40 ` wip-threads-and-fork Andy Wingo
2012-03-27 15:54 ` wip-threads-and-fork Ludovic Courtès
2012-04-06 18:30 ` wip-threads-and-fork Andy Wingo
2012-04-07 22:54 ` wip-threads-and-fork Ludovic Courtès
2013-01-17 11:41 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:32 ` wip-threads-and-fork Ludovic Courtès
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=8762el5qkx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).