Closed Bug 3506 Opened 26 years ago Closed 26 years ago

Bug in autoreg or services loader

Categories

(Core :: XPCOM, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: rickg, Assigned: dp)

Details

(Whiteboard: waiting for rick's OK)

1. Do a clean build (pull_all all) 2. Run viewer.exe from somewhere other than mozilla\win32_d.obj\bin (assume that it's in your path) 3. App crashes If you run it once from with the .\bin directory then all is well. It appears to be an init problem that gets persisted after the 1st run. (It's not really a netlib problem, but I wanted to make sure you got this bug).
Status: NEW → ASSIGNED
Component: Networking Library → XPCOM
Gotcha! Will see why this is happening. I think this has to do with components moving to the component/ direcotry whereas the NS_SetupRegistry() hack still just gives the dllname instead of components/dllname
Changing component to XPCOM
Target Milestone: M3
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
We use absolute path. This should work.
Rick, can you verify that this bug is fixed? It looks like a build problem, and we don't do our own builds. Thanks.
Whiteboard: waiting for rick's OK
Status: RESOLVED → VERIFIED
haven't heard from rick, will assume fixed and mark verified - please re-open if not.
You need to log in before you can comment on or make changes to this bug.