I'm running Digital Unix 4.0b on a 4100 with the jumbo patch
installed. In a threaded application (using pthreads), I set a signal
using
signal(SIGPIPE, SIG_IGN)
Later, somehow, I get a SIGPIPE error on a write to a socket.
I set my SIG_IGN before any threads are forked. From my reading of the
pthreads manual, that signal action should then be used for all
pthreads.
There are no other routines that set SIGPIPE in my application. When I
trace the __sigaction and _Esigaction and signal entry points, I see
that the pthreads libraries muck with signals considerably.
Does anyone know of a buglist for pthreads for this version of Digital
Unix? Is it possible that this version of the thread library might
acciddently re-enable the signal?
Received on Sun Oct 12 1997 - 21:15:29 NZDT