flatpak-spawn: Use exit code 70 for weird wait-statuses as intended
The original implementation mistakenly reset exit_status instead of
exit_code. This originally left exit_code undefined, with subsequent
commit 50991f5f "Fix (bogus) uninitialized use warning" changing the
undefined exit code to 0.
Revert 50991f5f, because the warning turned out not to have
been bogus, and should be silenced by this change.
I usually find that code dealing with POSIX-style exit statuses is
clearer if we distinguish between a "wait status" (what wait() or
waitpid() gives us, referred to as "wstatus" in Linux wait(2))
and an "exit status" (what we pass to exit(3), or equivalently, what
we can extract from a wait status with the WEXITSTATUS macro).
The last commit can be dropped if the flatpak-xdg-utils maintainers don't think it improves clarity.
flatpak-spawn: Use exit code 70 for weird wait-statuses as intended
The original implementation mistakenly reset exit_status instead of exit_code. This originally left exit_code undefined, with subsequent commit 50991f5f "Fix (bogus) uninitialized use warning" changing the undefined exit code to 0.
Revert 50991f5f, because the warning turned out not to have been bogus, and should be silenced by this change.
Fixes: 54c5800f "spawn: fix propagating exit code"
flatpak-spawn: Clarify a variable name
I usually find that code dealing with POSIX-style exit statuses is clearer if we distinguish between a "wait status" (what wait() or waitpid() gives us, referred to as "wstatus" in Linux wait(2)) and an "exit status" (what we pass to exit(3), or equivalently, what we can extract from a wait status with the WEXITSTATUS macro).
The last commit can be dropped if the flatpak-xdg-utils maintainers don't think it improves clarity.