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: Tue, 28 Mar 2017 05:25:58 +0300

> From: address@hidden
> Date: Mon, 27 Mar 2017 13:26:49 -0600
> Cc: address@hidden, address@hidden
> 
> Eli Zaretskii <address@hidden> wrote:
> 
> > > From: address@hidden
> > > Date: Mon, 27 Mar 2017 12:50:07 -0600
> > > Cc: address@hidden
> > > 
> > > I have set things up (I hope) so that gawk behaves like other awks and
> > > dies via SIGPIPE when that should happen. This then automatically
> > > has the exit status set to what it should be in POSIX systems.
> >
> > What does this mean for systems that don't have SIGPIPE?  You will
> > likely see a long series of EINVAL from the write routines there.
> 
> Gawk will exit FATAL. It should all work ok.

I'm not sure it will, but I don't think I see the whole picture yet.

Shouldn't we emulate an abnormal exit, as in "crash"?  EXIT_FAIL is
not it, it just means "some error".

> If you want a tarball let me know

Yes, please.  And also a script that could be used to test this
situation.

Thanks.



reply via email to

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