Re: GNAT: Setting SIGPIPE to SIG_IGN

[Darren New <dnew@san.rr.com>]

"Warren W. Gay VE3WWG" wrote:
> 
> Florian Weimer wrote:
> > I want to instruct the GNAT run-time library that it sets the SIGPIPE
> > handler to SIG_IGN, so that system calls such as read() return EPIPE
> > instead of delivering a signal.
> 
> Actually, I think you mean that read(2) returns EINTR (or EAGAIN
> on some platforms). EPIPE is returned when you write to a
> pipe without a reader.

If you read from a pipe whose other end has been closed, I'm pretty sure you
always get EOF, yes? Of course, if you get a different signal while blocked
on the pipe, you of course get the same signal you'd get from any blocking
operation that gets interruped by a signal.

It's writing to a broken pipe that raises SIGPIPE, and that's only because
of the funky way that UNIX shells cause signals to be delivered to
processes. (Basically, the original V7 shells wound up having the last
process of a pipeline being the direct child, and the shell passed signals
on to it, so it died, and the other processes in the pipeline died as they
tried to write to the broken pipe. Obviated by the invention of control
terminals.)

-- 
Darren New 
San Diego, CA, USA (PST). Cryptokeys on demand.
   ** http://images.fbrtech.com/dnew/ **

Try our EbolaBurgers...
      So tender they melt in your mouth.