On 3/21/09, Wan-Teh Chang <w...@google.com> wrote: > > 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 >
I have attempted this to the result of Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1810576496 (LWP 3177)] 0xb79e6547 in NSSSSL_VersionCheck () from /usr/lib/libssl3.so.1d (gdb) where #0 0xb79e6547 in NSSSSL_VersionCheck () from /usr/lib/libssl3.so.1d #1 0xb79e212d in SSL_GetStatistics () from /usr/lib/libssl3.so.1d I am very confused with this also. but thank you. John
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
