On Fri, 20 Mar 2009, Wan-Teh Chang wrote:
But I agree that SIGPIPE is an exception. This is why NSPR (a depenency of NSS) calls sigaction() to ignore SIGPIPE during initialization. Note that this is done for self protection, rather than as a documented service to the NSPR client.
But doesn't this then contradict what was just said? But why only during initilization? If it's fine to survive a dead peer during init and not signal anything, why isn't it later?
So the issue is why you receive SIGPIPE while calling NSSSSL_VersionCheck (). This implies that NSPR hasn't been initialized at that point.
John D, what is calling NSSSSL_VersionCheck() before th PR_Init() call? libcurl does nothing SSL at all before calling PR_Init() as far as I can see!?
-- / daniel.haxx.se -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
