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 08:40:12 +0300

> Date: Sat, 8 Apr 2017 23:47:58 +0200
> From: <address@hidden>
> CC: <address@hidden>, <address@hidden>
> 
> >>    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.
> 
> So, you'd draw a hard line between the two values 0xC0000008 and 0xC000014B ?

I'm drawing a line where the EXCEPTION_* values defined in winbase.h
header end.  All the other values are AFAIK never triggered by fatal
exceptions that cause abnormal program termination.

> Seriously, that looks like some ego-driven quest now.

Not on my side.  I was just answering your questions.



reply via email to

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