Closed
Bug 89139
Opened 24 years ago
Closed 24 years ago
nsNSSComponent::RegisterProfileChangeObserver() returns garbage
Categories
(Core Graveyard :: Security: UI, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.0
People
(Reporter: mikepinkerton, Assigned: ddrinan0264)
References
Details
(Whiteboard: nsbranch+; PDT+)
Attachments
(1 file)
871 bytes,
patch
|
Details | Diff | Splinter Review |
nsNSSComponent::RegisterProfileChangeObserver() returns a result from an
uninitialized variable:
nsresult
nsNSSComponent::RegisterProfileChangeObserver()
{
nsresult rv;
nsCOMPtr<nsIObserverService>
observerService(do_GetService(NS_OBSERVERSERVICE_CONTRACTID));
NS_ASSERTION(observerService, "could not get observer service");
if (observerService) {
observerService->AddObserver(this, PROFILE_BEFORE_CHANGE_TOPIC);
observerService->AddObserver(this, PROFILE_AFTER_CHANGE_TOPIC);
}
return rv;
}
|rv| is never given a value. this is a compiler warning on mac, but can have
serious side effects if someone is checking this return value.
Comment 1•24 years ago
|
||
PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.0
Comment 2•24 years ago
|
||
setting nsbranch. This looks like something that's easy to fix.
t-> 2.0
Priority: -- → P2
Whiteboard: nsbranch
Target Milestone: --- → 2.0
Assignee | ||
Comment 3•24 years ago
|
||
Comment 4•24 years ago
|
||
r=walk84
Comment 5•24 years ago
|
||
sr=blizzard
Assignee | ||
Comment 6•24 years ago
|
||
Fix checked into trunk.
Comment 7•24 years ago
|
||
Marking fixed per ddrinan's comment. How can this be verified?
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 8•24 years ago
|
||
returning a known value is clearly better than returning an uninitialized value.
Can we get PDT+ on this one?
Keywords: vtrunk
Whiteboard: nsbranch → nsbranch+ want PDT plus
Comment 9•24 years ago
|
||
PDT+ as per 07/09/2001 PDT meeting.
Whiteboard: nsbranch+ want PDT plus → nsbranch+; PDT+
Comment 10•24 years ago
|
||
verified checked in the branch. v1.44.4.1
There is no known problem to verify this against.
-> verified.
Status: RESOLVED → VERIFIED
Comment 11•24 years ago
|
||
*** Bug 83264 has been marked as a duplicate of this bug. ***
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•