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: arnold
Subject: Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]
Date: Sun, 09 Apr 2017 01:41:58 -0600
User-agent: Heirloom mailx 12.4 7/29/08

Eli Zaretskii <address@hidden> wrote:

> > 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.

Hi All.

Eli - thanks for fix. Alexandre, thanks for the discussion.

It's clear there isn't a perfect mapping here. This looks like
a reasonable compromise.

Let's close off the discussion now, please.

Thanks,

Arnold



reply via email to

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