Set the default SIGPIPE handler before starting bash. #135
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.
A couple of standard unix tools like
head
will close the stdin once finished without reading the full contents of the input. This enables idiomatic processing of infinite files like/dev/urandom
.Currently the bash_kernel hangs infinitely or reports broken pipe errors while executing such code.
To reproduce the issue, execute
cat /dev/urandom | tr -dc '[:alpha:]' | fold -w ${1:-20} | head -n 1
This will print the output but will hang infinitely.tr -dc '[:alpha:]' </dev/urandom | head -c 10
This will print the output with additional broken pipe error messages.Root cause of the issue is that Python uses its own signal hander for SIGPIPE to let detecting broken pipes with Python exceptions.
Fix: While temporarily switching to the default SIGINT handler, let's switch to the default SIGPIPE handler too.