You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A straightforward way to avoid this on Unix is to use a socketpair rather than a pipe for sending input to the subprocess. Still use pipes within a pipeline, of course - there, the SIGPIPE behavior is correct. But pipes are optimized for pipelines, and for other communication with a subprocess it's better to use a socketpair.
The text was updated successfully, but these errors were encountered:
catern
changed the title
Use socketpairs for stdinCatching pipe errors when writing to standard input - use socketpai
Use socketpairs for stdin
Oct 12, 2023
Catching pipe errors when writing to standard input
A straightforward way to avoid this on Unix is to use a socketpair rather than a pipe for sending input to the subprocess. Still use pipes within a pipeline, of course - there, the SIGPIPE behavior is correct. But pipes are optimized for pipelines, and for other communication with a subprocess it's better to use a socketpair.
The text was updated successfully, but these errors were encountered: