Closed Bug 473232 Opened 17 years ago Closed 17 years ago

Outparam writing analysis doesn't handle nsCOMPtr::swap

Categories

(Developer Infrastructure :: Source Code Analysis, defect)

Product:
Developer Infrastructure
Component:
Source Code Analysis
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: sdwilsh, Unassigned)

Details

I noticed I was getting blamed for some outparm warnings that seemed bad. After invesitaging them, I noticed it was because I was using nsCOMPtr's swap method to avoid reference counting. The analysis script doesn't think it's being written to when it actually is.
Should be easy enough to fix. Could you please give me a small test case?
Nevermind - turns out I was using swap wrong and just didn't know it!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Product: Core → Firefox Build System
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.