Hello,
I have an NSS/NSPR server app that listens for client connection requests and that creates a new thread using PR_CreateThread() to handle each new client connection.
The problem is that this app has a memory leak, somewhere. And I can't seem to find the leak.
So I got hold of the latest version of Purify and instrumented my app.
But when I run my app with Purify, it seems that I get a boatload of problem reports concerning memory management (e.g., reading uninitialized memory) in the NSS and NSPR libraries.
If the uninitliazed memory is read by an NSS or NSPR function *directly*, this should be reported as a bug report.
If the uninitialized memory is read by a system function called by NSS or NSPR, this is either a bug in the system function or a bug in the Purify.
Wan-Teh
