Closed
Bug 845613
Opened 12 years ago
Closed 12 years ago
Locking issues in the write poisoning code
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: espindola, Assigned: espindola)
References
Details
Attachments
(1 file, 2 obsolete files)
5.97 KB,
patch
|
BenWa
:
review+
|
Details | Diff | Splinter Review |
I found 3 issues while working on 845098:
* Using a local static in getDebugFDsLock, which is not safe on windows.
* Lock not held while deleting the std::vector with debug fds
* We have a copy in mozPoisonWriteMac.cpp :-(
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #718772 -
Flags: review?(bgirard)
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #718772 -
Attachment is obsolete: true
Attachment #718772 -
Flags: review?(bgirard)
Attachment #719043 -
Flags: review?(bgirard)
Assignee | ||
Comment 3•12 years ago
|
||
Attachment #719043 -
Attachment is obsolete: true
Attachment #719043 -
Flags: review?(bgirard)
Attachment #719101 -
Flags: review?(bgirard)
Updated•12 years ago
|
Attachment #719101 -
Flags: review?(bgirard) → review+
Assignee | ||
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•