bug-gawk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]


From: Eli Zaretskii
Subject: Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]
Date: Sun, 09 Apr 2017 00:15:35 +0300

> Date: Sat, 8 Apr 2017 21:25:30 +0200
> From: <address@hidden>
> CC: <address@hidden>, <address@hidden>
> 
> > They will not know that this was caused by a broken pipe, but they
> > will know (a) that the program exited abnormally, and (b) that the
> > abnormal exit was caused by some handle becoming invalid.  That's
> > close enough, and I just didn't find any better way.
> 
> In the meantime I've found this one:
> 
>   0xC000014B   STATUS_PIPE_BROKEN
> 
> Do you really think "invalid handle" better conveys that meaning ?

Yes, because AFAIK STATUS_PIPE_BROKEN is a status returned by device
drivers, not by programs.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]