[sanitizer_common] Fix SIGPIPE when symbolizer started by StartSubprocess dies #171511
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.
It's possible for the sanitized process to get SIGPIPE if the symbolizer dies. To prevent this from happening, #170809 added a field to SymbolizerProcess that can hold the read end of the child's stdin. This keeps the read end of the stdin pipe open for the lifetime of the SymbolizerProcess, which prevents us from getting SIGPIPE.
#170809 only uses this field on the posix_spawn path. This PR makes the change to the StartSubprocess path as well.
Closes #120915