Re: crash (unhandled SIGPIPE) on write to closed file descriptor

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: crash (unhandled SIGPIPE) on write to closed file descriptor
Date	2019-07-22 11:28 -0400
Message-ID	<mailman.2000.1563809346.2688.bug-bash@gnu.org> (permalink)
References	<CAB7qRiXPdTXG290dPi70toEDfR_2+2Cf3GUbvzrWaP6wFNovmw@mail.gmail.com> <66df6798-b6d0-40ad-68f7-ef1738c69d53@case.edu>

Show all headers | View raw

On 7/20/19 2:05 PM, Bonjour Abracadraba wrote:

> Bash Version: 5.0
> Patch Level: 3
> Release Status: release
> 
> Description:
> 	Bash 2.04 through 5.0 crash when trying to write to a closed socket.
> It is expected for bash to give an user error, but it exits instead.

This seems like user error. The script's actions caused the socket to
close, the next write generates SIGPIPE as a result, and SIGPIPE is a fatal
signal.

If you want the script to survive the SIGPIPE it generates, trap SIGPIPE.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: crash (unhandled SIGPIPE) on write to closed file descriptor Chet Ramey <chet.ramey@case.edu> - 2019-07-22 11:28 -0400

csiph-web