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

[alexandre.ferrieux]

On 08/04/2017 23:15, Eli Zaretskii wrote:
> >  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.

So, you'd draw a hard line between the two values 0xC0000008 and 0xC000014B ?
Seriously, that looks like some ego-driven quest now.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.