From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Subject: Re: primitive-fork hang
Date: Tue, 08 Mar 2005 18:05:24 +0100 [thread overview]
Message-ID: <ljsm36rru3.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <87acpoqr42.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 01 Mar 2005 09:03:41 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>>
>> Does it still fail for you?
>
> Yes. I'm not sure if it's something I've done. I had trouble getting
> gdb to show anything.
I remember seeing strange blocking as well, and I think it was because
some pipe wasn't being closed properly in the parent or child. That
open pipe prevented one of the parties from seeing EOF, or something
like that.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-03-08 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 22:48 ash rewrite Kevin Ryde
2005-01-27 22:50 ` Kevin Ryde
2005-02-09 21:29 ` Rob Browning
2005-02-09 22:16 ` Kevin Ryde
2005-02-09 22:33 ` primitive-fork hang (was: ash rewrite) Kevin Ryde
2005-02-28 1:50 ` primitive-fork hang Marius Vollmer
2005-02-28 22:03 ` Kevin Ryde
2005-03-08 17:05 ` Marius Vollmer [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=ljsm36rru3.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
/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).