Pull from evening of March 9, 1999, NSPR build from March 8, 1999. Solaris 2.6, gcc 2.7.2.3, purify. Happens during apprunner startup. PAR: Bad function parameter: * This is occurring while in: DLOpEN [rtlib.o] PR_LoadLibrary [prlink.c:700] nsDll::Load() [xcDll.cpp:150] nsComponentManagerImpl::LoadFactory(nsFactoryEntry*,nsIFactory**) [nsComponentManager.cpp:797] nsComponentManagerImpl::FindFactory(const nsID&,nsIFactory**) [nsComponentManager.cpp:903] nsComponentManagerImpl::CreateInstance(const nsID&,nsISupports*,const nsID&,void**) [nsComponentManager.cpp:1061] nsComponentManager::CreateInstance(const nsID&,nsISupports*,const nsID&,void**) [nsRepository.cpp:67] nsServiceManagerImpl::GetService(const nsID&,const nsID&,nsISupports**,nsIShutdownListener*) [nsServiceManager.cpp:229] nsServiceManager::GetService(const nsID&,const nsID&,nsISupports**,nsIShutdownListener*) [nsServiceManager.cpp:391] nsWebShell::CreatePluginHost(int) [nsWebShell.cpp:406] nsWebShell::Init(void*,int,int,int,int,nsScrollPreference,int,int) [nsWebShell.cpp:727] nsWebShellWindow::Initialize(nsIWidget*,nsIAppShell*,nsIURL*,nsString&,nsIStream Observer*,nsIXULWindowCallbacks*,int,int) [nsWebShellWindow.cpp:227] nsAppShellService::CreateTopLevelWindow(nsIWidget*,nsIURL*,nsString&,nsIWidget*& ,nsIStreamObserver*,nsIXULWindowCallbacks*,int,int) [nsAppShellService.cpp:233] main [nsAppRunner.cpp:275] _start [crt1.o] * dlopen("raptorplugin.so", 257) file (arg #1) not found.

New bugs should be assigned to module owners.

The PR_LoadLibrary funtion passes the input argument (the dll name), unmodified, to the dlopen() function; the purify output says that the dll "raptorplugin.so" doesn't exist. This isn't due to a bug in nspr.

Re-assigning to XPCOM Registry since that is the code that calls this code.

I dont understand this. The function parameter is bad. Bruce do you still see this. Marking M5 since there doesn't seem to be any effect of this yet.

This was happening because we were trying to load some libraries that didn't exist. Since this particular library load was fixed to load the libraptorplugin, it is fine. More worrisome were the 2 invalid pointer errors that happened after this one. Purify outputs this error here because it has to trap dlopen() calls and instrument libraries if necessary. The related bug report is bug #3577. With all of this in mind, I'd be tempted to flag this bug as Resolved/Invalid and spend time figuring out bug #3577.

What did I miss? When did this get fixed? I still see these errors I think.

bruce, do you still see these errors during startup?

amazing but true. these finally seem to have stopped.