Closed
Bug 6534
Opened 26 years ago
Closed 26 years ago
nsComponentManager::RegisterComponent returns bogus value
Categories
(Core :: XPCOM, defect, P1)
Tracking
()
RESOLVED
FIXED
M7
People
(Reporter: erik, Assigned: dp)
Details
nsComponentManager::RegisterComponent returns a bogus value. The manual
registrations in NS_SetupRegistry do not check the return value, so they never
notice, but I recently added some return value checking code, and I did bump
into it. nsComponentManagerImpl::HashProgID is returning an error if aProgID
is NULL.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Component: XPCOM Registry → XPCOM
Priority: P3 → P1
Target Milestone: M7
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 1•26 years ago
|
||
Returning proper values now. Added a check to make sure we do Progid caching
only if progid is not null.
You need to log in
before you can comment on or make changes to this bug.
Description
•