We have never used the explicit load function on any of the operating systems we use, we always implicitly load (The shared library or shared library stub is linked with the actual executable).
I would stick with NSS 3.2 or NSS 3.3 binaries for any experiments. Be sure you aren't mixing version of NSS (you don't have some other version statically linked with our application). Since we don't actually support this method of using NSS, it's quite possible there are problems, but I would have predicted that it should work, as long as you remember to initialize NSS before you start calling other NSS functions. I'd make sure the application works with the implicit loading first. you can look at the Makefiles in security/mozilla/cmd to see you to set up your link line. bob Kenneth R. Robinette wrote: > I am trying to load the NSS-3.1.1 window dll's nss3.dll, plc4.dll and > nspr4.dll with the Windows LoadLibrary function. The loads appear to > function correctly, however my applicaton always aborts a few seconds after > using several of the functions contained within the subject dll's. > > I tried using the NSS-3.3 dll's distributed in binary form and get the same > result. > > If I link instead using the .libs for each of the above dll's, all works > perfect. > > Is there a known problem linking NSS in a dynamic manner. > > Ken > > > >
