Kevin Ryde <[EMAIL PROTECTED]> writes: > Actually, I see the signalling pipe is left in the parent, so if the > child has printed nothing it could hang. Obviously there's something > wrong if the child doesn't print what's expected, but the change below > should at least cause an error instead of a hang in that case.
OK, here's what I see with that test code: Running popen.test FAIL: popen.test: open-output-pipe: no duplicate FAIL: popen.test: close-pipe: exit 0 ERROR: popen.test: close-pipe: exit 1 - arguments: ((wrong-number-of-args #f "Wrong number of arguments to ~A" (#<procedure #f (pt-entry)>) #f)) ERROR: In procedure fport_flush: ERROR: Bad file descriptor ERROR: In procedure fport_flush: ERROR: Bad file descriptor Running ports.test -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
