Scott Lamb wrote:
> You could just do a pthread_sigmask() before and after the
> pthread_setspecific() to guarantee that no SIGPIPE will arrive on that
> thread in that time. I think it's pretty safe to assume that as long as
> you're not doing a pthread_[gs]etspecific() on that same pthread_key_t,
> it's safe.
I call pthread_setspecific() in the SIGPIPE handler. How sdoes
pthread_sigmask() help me at that point?
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073