Hello,

I've been looking the sample client at
mozilla\security\nss\cmd\SSLsample\client.c, and I can't seem to
figure how the function
reap_threads( &threadMGR ) works...

The client will block upon calling reap_threads() in client_main().
Upon inspection of reap_threads() in the accompanying file called
sslsample.c,
the block happens upon calling PR_WaitCondVar( threadMGR->threadEndQ,
PR_INTERVAL_NO_TIMEOUT ), which I believe means the thread entered a
monitor and is waiting on a condition variable... But PR_WaitCondVar()
never returns which means some condition variable is not being
notified somewhere...

How do I get the client to return from reap_threads() so it can then
call destroy_thread_data() and exit properly?

BTW, I'm launching this client app from the command line and it's
talking to the selserv app under mozilla\security\nss\cmd\selfserv.

-- POC
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto

Reply via email to