Kevin Ryde <[EMAIL PROTECTED]> writes:
> Looks about right. What's the child process doing? It's supposed to
> be writing to the parent to say continue. (Unless it failed to fork
> there should be some child, either running or a zombie.)
(Consider the following info preliminary. I haven't had
Rob Browning <[EMAIL PROTECTED]> writes:
>
> ;;(dbg-out (list 'pt-entry pt-entry))
> ...
>
> ERROR: popen.test: open-output-pipe: no duplicate - arguments:
> ((wrong-type-arg "list-copy" "Wrong type argument in position ~A: ~S"
>
Kevin Ryde <[EMAIL PROTECTED]> writes:
> I suppose that's the killer, a port gc-ed prematurely. Perhaps
> there'd be some significance in which one it was. port-for-each
> looks pretty safe, maybe the port table has gone bad earlier.
I think I found the problem. I believe scm_c_port_for_each()
