Closed Bug 280889 Opened 15 years ago Closed 15 years ago
cursor can be used uninitialized in ns
Event State Manager::Update Cursor
If aTargetFrame is null then cursor can be used uninitialized in some cases in nsEventStateManager::UpdateCursor.
Caught using /RTCu windows compiler option, uninitialized use seen in action. If aTargetFrame is null we don't try to set the real cursor to this value, but it is used in a couple comparisons still.
Comment on attachment 173236 [details] [diff] [review] initialize cursor Shouldn't that be !CheckDisabled ?
Of course it should be (I blame the codeine). Thanks!
Attachment #173236 - Attachment is obsolete: true
Comment on attachment 173245 [details] [diff] [review] correct version r+sr=bzbarsky
Also found by Coverity
Whiteboard: Coverity UNINIT
Checked into trunk
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.