Skip to content

fix(proc): a lost exit status is an error, not signal 9 - #6

Merged
HaoZeke merged 12 commits into
mainfrom
fix/proc-wait-status
Nov 16, 2026
Merged

HaoZeke merged 12 commits into
mainfrom
fix/proc-wait-status

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

proc.run returns error.NoChild when the child's status is lost because the caller ignores SIGCHLD.

  • reap turned any wait4 failure into a kill by signal 9. With SIGCHLD ignored the kernel reaps the child and wait4 fails with ECHILD, so run reported a SIGKILL for a child that exited normally.
  • reap now returns the wait4 error through sys.call, run returns error.NoChild with sys.last_errno set, and run's doc says not to ignore SIGCHLD. The error paths still reap and keep their own error.
  • The test sets SIGCHLD to SIG_IGN, expects error.NoChild, and fails until reap returns the wait4 error.

The branch has a CHANGELOG Unreleased entry.

fgetxattr was not retried on EINTR, so a signal refused the replacement.
atomicWrite also leaked the temporary path, the step names and the spare
ACL read. Tests cover both under std.testing.allocator.
copyTo renames the new bytes into place, so a full disk or a file-size
limit leaves an existing file unchanged. appendLine rolls a short write
back to the size before it, so the line list does not gain a partial line.
lockExclusive reads its deadline from the monotonic clock, so a signal
that cuts a sleep short does not expire the wait. RootLock refuses a gate
or sidecar that is not a regular file of this user with one link.
decodeCache and key comparison read past a string that ended on a
backslash. They now return an encoding error, and the bytes allocated
before that error are freed.
The list was abandoned on the error path, and the slice it returned was
not the whole allocation, so a caller could not free it.
The archive is written under a temporary name, synced and renamed. A
crash or a short write no longer leaves a partial name.gz that a later
run skips.
groupAlive treated EINTR from getdents as "nobody is alive", so
waitGroupGone could return while the group was still running.
COMPAT.md said errno 134 was the unnamed hardware-error text. On x86_64
that text is errno 133, HWPOISON, which Zig names; 134 is unnamed, as
glibc prints it. The module summary matches the copy and the lock gate.
A caller started with fd 0, 1 or 2 closed gets /dev/null at that number.
With fd 1 closed the child's stderr ends up in the captured stdout; with
fd 0 or 2 closed the child loses that stream at exec. Each test forks,
closes the descriptor and checks what the child sees. They fail until
childExec is fixed.
…reams

When the caller started with fd 0, 1 or 2 closed, /dev/null or a pipe took
that number, and childExec's dup2 sequence either clobbered it (fd 1: the
child's stderr went to the captured stdout) or made a no-op dup2 onto
itself that kept close-on-exec (fd 0 or 2: the child started with that
stream closed). Sources below 3 now move above 2 before the dup2s, as
Python's _posixsubprocess does.
With SIGCHLD set to SIG_IGN the kernel reaps the child itself and wait4
fails with ECHILD. reap reports that as a kill by signal 9, so a child
that exited 3 reads as SIGKILLed. The test expects error.NoChild and
fails until reap returns the wait4 error.
reap turned any wait4 failure into a kill by signal 9. With SIGCHLD
ignored the kernel reaps the child and wait4 fails with ECHILD, so run
reported a SIGKILL for a child that exited normally. reap now returns the
wait4 error through sys.call, run returns error.NoChild with
sys.last_errno set, and run's doc says not to ignore SIGCHLD. The error
paths still reap and keep their own error.
@HaoZeke
HaoZeke force-pushed the fix/proc-wait-status branch from 8af7958 to de97e8f Compare November 16, 2026 08:16
@HaoZeke
HaoZeke merged commit f99c621 into main Nov 16, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant