Closed
Bug 71921
Opened 25 years ago
Closed 25 years ago
nsInputStreamTee::WriteSegmentFun has a minor bug
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla0.9
People
(Reporter: darin.moz, Assigned: darin.moz)
Details
Attachments
(1 file)
|
821 bytes,
patch
|
Details | Diff | Splinter Review |
nsInputStreamTee::WriteSegmentFun compares writeCount to zero when it should
really be comparing *writeCount to zero. This has led to all sorts of data
corruption.
|
Assignee | |
Updated•25 years ago
|
|
|
Assignee | |
Comment 1•25 years ago
|
||
|
|
Assignee | |
Comment 2•25 years ago
|
||
Actually, I was mistaken about the severity of this bug. writeCount is almost
always non-zero, and there is no harm (other than missing out on a small
optimization) in not having the (*writeCount == 0) test. So, this bug is
really very minor.
Severity: normal → minor
|
|
Assignee | |
Updated•25 years ago
|
Keywords: patch
Summary: nsInputStreamTee::WriteSegmentFun is broken → nsInputStreamTee::WriteSegmentFun has a minor bug
|
|
Assignee | |
Comment 3•25 years ago
|
||
dougt says "sr"
|
|
Assignee | |
Comment 4•25 years ago
|
||
fix checked in
|
|
Assignee | |
Comment 5•25 years ago
|
||
marking FIXED
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•