[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]
From: |
alexandre.ferrieux |
Subject: |
Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH] |
Date: |
Sun, 9 Apr 2017 13:35:10 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111113 Thunderbird/8.0 |
On 09/04/2017 13:04, Eli Zaretskii wrote:
> How many of them will stop and not use Google ? Seriously ...
Programs don't use Google. They use values encoded in their source
code.
Aha, here is the mental process of the human writing that source code:
Proactive case:
(1) I want to isolate the case where gawk exits due to a broken pipe
(2) Hmm, what is the Windows way of saying that ?
(3) ( googling / grepping headers )
(4) Found: 0xC000014B STATUS_PIPE_BROKEN => I'll use that one
(5) Hmm, that doesn't work. I'll add some debug to see.
(6) Oh, turns out exit status is 0xC0000008 . What does that mean ?
(7) ( googling / grepping headers )
(8) Found: 0xC0000008 EXCEPTION_INVALID_HANDLE => wtf ?
(9) Looks like gawk shoots its feet while handling broken pipes on
Windows; I'll report that to them.
Or maybe I'll use some other equivalent scripting language in between, since I
assume such a deep bug takes ages to fix.
Reactive case:
(1) Hmm, my big application dies quickly in that situation. Why ?
(2) I'll add some debug to see. Start with subprocess start/stop and
exit statuses.
(3) Aha ! The third gawk out of seven dies with 0xC0000008. What does
that mean ?
(4) ( googling / grepping headers )
(5) Found: 0xC0000008 EXCEPTION_INVALID_HANDLE => wtf ?
(6) This looks like a deep internal error. I have no time to chase that one. I will post a bug report to gawk. Or maybe
I'll use some other equivalent scripting language in between, since I assume such a deep bug takes ages to fix.
Is that what you want ?
_________________________________________________________________________________________________________________________
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.
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], (continued)
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/08
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/08
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/08
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/08
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], arnold, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH],
alexandre.ferrieux <=
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], Eli Zaretskii, 2017/04/09
- Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH], alexandre.ferrieux, 2017/04/09