From: Robert Marlow <bobstopper@australispro.com.au>
Subject: Re: Threads + pipes = bad?
Date: 31 Jul 2003 16:20:05 +0800 [thread overview]
Message-ID: <1059639605.18804.9.camel@helicon> (raw)
In-Reply-To: <87u196l01k.fsf@zip.com.au>
My main process just brings up a few threads and then sits back in a
while loop doing nothing.
Actually, select's throwing file number errors at me as well. It seems
whenever I use a port, if it's outside a mutex lock it complains.
On Tue, 2003-07-29 at 07:11, Kevin Ryde wrote:
> Does your main thread do anything evil? Without actually trying it,
> it seems that open-process might end up with all threads still running
> in the forked child (until it exec's).
--
Regards,
Robert Marlow
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2003-07-31 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 7:48 Threads + pipes = bad? Robert Marlow
2003-07-24 15:07 ` Robert Marlow
2003-07-28 23:11 ` Kevin Ryde
2003-07-31 8:20 ` Robert Marlow [this message]
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=1059639605.18804.9.camel@helicon \
--to=bobstopper@australispro.com.au \
/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).