This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Robustify fork server launching & problem detection, part 1 #536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Robustify fork server launching & problem detection, part 1
This change addresses the problems (1) and (4) from the bug:
The fork server launches the command in the background like this:
However,
system()
always returns success in this case, provided it can just parse the command, because the command is run in the background and doesn't return its exit code to the subshell.Even if started successfully, the fork server can still die at any moment. Centepede doesn't attempt to detect this, instead sending execution requests to an absent process, never receiving a reply, and eventually timing out.