Closed
Bug 9311
Opened 26 years ago
Closed 25 years ago
nsStringOutputStream does not properly handle null-named streams
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
WONTFIX
People
(Reporter: mcafee, Assigned: mcafee)
References
Details
This bug comes from http://bugzilla.mozilla.org/show_bug.cgi?id=6098.
Solaris: first-time startup caused crash, workaround checked in.
mString gets initialized, and then shows up NULL for the write() call.
[comments from 6098]:
nsStringOutputStream is designed to accept a null input string, and apparently
does not handle it correctly. Initializing it with a nonempty string first (one
whose contents are irrelevant...) may work around the problem, but it does not
solve the real problem.
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M11
|
|
Assignee | |
Updated•26 years ago
|
QA Contact: mcmullen → leger
|
|
Assignee | |
Updated•26 years ago
|
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M11 → M14
|
|
Assignee | |
Comment 1•26 years ago
|
||
not for beta
Component: Browser-General → Networking-Core
OS: Mac System 8.0 → Solaris
QA Contact: leger → mcafee
Hardware: PC → Sun
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M14 → M20
|
|
Assignee | |
Comment 4•26 years ago
|
||
This is still technically a problem, but no one
seems to be hitting it right now. m20.
|
|
Assignee | |
Comment 5•25 years ago
|
||
Ok, off the radar. marking won't fix.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
VERIFIED: reopen if you need hull-handling to work...
Status: RESOLVED → VERIFIED
Summary: Solaris does not properly handle null-named streams → nsStringOutputStream does not properly handle null-named streams
You need to log in
before you can comment on or make changes to this bug.
Description
•