It is an application's responsibility to call sigaction to ignore
SIGPIPE. You can do that with the following code:
#include <signal.h>
struct sigaction sigact;
sigact.sa_handler = SIG_IGN;
sigemptyset(&sigact.sa_mask);
sigact.sa_flags = 0;
sigaction(SIGPIPE, &sigact, NULL);
But your stack trace shows that NSPR should have been
initialized at that point. (The SSL_GetStatistics,
NSSSSL_VersionCheck functions in the call stacks can't
be trusted because you're using a release/optimized build
of NSS.) So NSPR's initialization function should have
called sigaction to ignore SIGPIPE. I don't know why
SIGPIPE isn't being ignored.
In any case, it is worth a try for your app to call sigaction
to ignore SIGPIPE using the code snippet I showed above.
Wan-Teh
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
