scsh-process/tests, branch 1.7.1Egg to add Scheme Shell process notation to CHICKEN Scheme.
https://code.more-magic.net/scsh-process/atom?h=1.7.12025-07-02T12:41:53ZFix cleanup handling in wait for processes forked without scsh-process2025-07-02T12:41:53ZPeter Bexpeter@more-magic.net2025-07-02T12:41:53Zurn:sha1:4a9adfd4591ca5de96b1294cd47d12c4efc22535
Similar to the C5 code, here we assumed that proc+condition would be
true if the pid-or-process argument was a raw pid number, as taken
from the table maintained by scsh-process.
Unfortunately, this assumption only holds when the process would've
been forked using "fork" from the scsh-process egg. If one forked
with the "core" fork from CHICKEN itself, both p and pending-before
would be false, which would lead to a "(car) bad argument type: #f"
error.
Reported by Matthew Welland.
Port to CHICKEN 62025-02-07T09:50:29ZPeter Bexpeter@more-magic.net2025-02-07T09:50:29Zurn:sha1:5d2659453493d7a1de7b80257763c72236c4008f
This allows us to reduce the code considerably because CHICKEN 6 now
has native process objects, so we don't need to keep our own version
of process tracking.
Note that we still need to keep our own list of child processes
created by "fork", because we want the automatic subprocess reaper to
be able to work in a thread. This means we still need to have a
central mapping of our own subprocesses to condition object so we can
signal the thread which is waiting.
After all I'm not so sure if this was such a great idea, but it's kind
of a neat feature that could be useful, so keep it for now.
Fix issue with redirection in run/port (and, by extension, run/string)2021-09-14T11:54:29ZPeter Bexpeter@more-magic.net2021-09-14T11:54:29Zurn:sha1:eb97f7d4f6a6428b52f6cd24e54d3e4650f631a0
We would initially create a pipe, dup(2) that onto fd 1 in the forked
process and open an output port on the original fd. This resulted in
a pretty nasty bug: if the fd would be redirected (by number) later,
it would not affect the output port because that was set up to point
to the original fd.
Instead, open an output port to the newly set up stdout and close the
direct pipe port.
Port scsh-process to CHICKEN 52018-08-16T20:41:12ZPeter Bexpeter@more-magic.net2018-08-16T20:41:12Zurn:sha1:dd7d5a27716ca0c02314487711f6a9cb32731440
Thanks to Vasilij Schneidermann for providing an initial patch.
Wrap tests in module to make porting easier2018-08-16T20:00:05ZPeter Bexpeter@more-magic.net2018-08-16T20:00:05Zurn:sha1:b36f392a9a09bb666390260311df358c54cc0f8bDrop bogus test2018-08-16T19:59:29ZPeter Bexpeter@more-magic.net2018-08-16T19:59:29Zurn:sha1:8362d124fa8df2c6fafd677c16f72facebe8ee1f
run*/string* does not exist, and run/string* doesn't raise an
exception on nonzero exit status.
Make ">" redirect truncate existing files2018-04-21T08:40:07ZPeter Bexpeter@more-magic.net2018-04-21T08:40:07Zurn:sha1:e0a136839ff1f359f01320e2c3e32bae0164b785
Thanks to Joerg Wittenberger
Fix ordering of (= x y) redirection EPF2018-01-26T21:25:23ZPeter Bexpeter@more-magic.net2018-01-26T21:25:23Zurn:sha1:a7fd28ee34353eac9502782ceb0ed3961026f284
Thanks to Diego "dieggsy" for pointing out this incongruity with
scsh-process.
Run signal handler in a separate thread2017-11-18T12:58:13ZPeter Bexpeter@more-magic.net2017-11-18T12:58:13Zurn:sha1:1adc1af6d9b52ad33f0b773cfdcd64573a2b7b9e
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.
Also unmask (if needed) sigchld in the child process thunk2017-11-10T20:08:02ZPeter Bexpeter@more-magic.net2017-11-10T20:08:02Zurn:sha1:4e420e4d032b550fa6e0193a3bbf04f4db76cc8b
This would be otherwise kept in masked mode because the thunk is in
the dynamic extent of the dynamic-wind.