Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15198 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-22 11:28 -0400 |
| Last post | 2019-07-22 11:28 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: crash (unhandled SIGPIPE) on write to closed file descriptor Chet Ramey <chet.ramey@case.edu> - 2019-07-22 11:28 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-22 11:28 -0400 |
| Subject | Re: crash (unhandled SIGPIPE) on write to closed file descriptor |
| Message-ID | <mailman.2000.1563809346.2688.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web