scsh-process, branch 1.2.0

Bump version to 1.2.0

2017-12-09T11:25:10Z

Do not redirect stderr to stdin in fork/pipe.

2017-12-09T11:23:41Z

Signed-off-by: Peter Bex

Tag 1.1.0

2017-11-18T13:31:26Z

Run signal handler in a separate thread

2017-11-18T12:58:13Z

This seems to be necessary so that condition-variable-broadcast! works when the signal handler is running in the same thread as the waiting thread.

Perform trial wait with "nohang" set to #t when blocking

2017-11-18T12:19:28Z

We might have missed the one and only SIGCHLD event for the process we're about to wait for, so attempt to reap it before entering the condition variable wait loop. Just in case, we always do this when we're woken up, so that we can't accidentally miss the signal.

Tag 1.0.0

2017-11-10T20:10:28Z

Also unmask (if needed) sigchld in the child process thunk

2017-11-10T20:08:02Z

This would be otherwise kept in masked mode because the thunk is in the dynamic extent of the dynamic-wind.

Don't unmask signal if the signal was already masked before forking

2017-11-10T20:03:18Z

Tag 0.9.0

2017-11-09T20:33:50Z

Temporarily mask sigchld to avoid race condition in fork

2017-11-09T20:26:48Z

We do a fork, and immediately afterwards we insert a scsh-process object into the pending processes table with the pid of the newly created child process. However, sigchld may arrive in between the fork and the insertion of the scsh-process object into the pending process table. The sigchld handler will reap the child process and attempt to update the pending scsh-process object, but it can't find it yet because the insertion of this object into the table happens after the fork, thus losing the reaped child's exit status. Then, if the program waits for the process after that, we enter an infinite busy waiting loop that expects a sigchld to arrive and update the object through the table, but that never happens because the child has already been reaped.