On Wed, Oct 03, 2012 at 06:21:45PM +0200, Peter Bex wrote:
> Hi all,
>
> I'm trying to figure out the behavior of process-fork and the
> handling of signal/chld (SIGCHLD). Here's a simple program
> which simply sets up a pipe and forks. The parent process reads
> from the pipe, the child writes to it.
[program elided]
> This program works just fine and prints ("hello, world").
> If I uncomment the signal handler code (which should just be a no-op),
> it hangs. I don't understand the reason for this. Could anyone
> enlighten me as to what's happening here?
Turns out this was a bug in Chicken core's handling of EINTR in getc()
calls:
http://lists.nongnu.org/archive/html/chicken-hackers/2012-10/msg00010.html
Cheers,
Peter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
is especially attractive, not only because it can be economically
and scientifically rewarding, but also because it can be an aesthetic
experience much like composing poetry or music."
-- Donald Knuth
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users
