Closed Bug 9311 Opened 25 years ago Closed 24 years ago

nsStringOutputStream does not properly handle null-named streams

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
Sun
Solaris
Type:
defect

Tracking

()

Status:
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.
Target Milestone: M11
QA Contact: mcmullen → leger
Component: XP File Handling → Browser-General
Depends on: 13916
OS: Linux → Mac System 8.0
Target Milestone: M11 → M14
not for beta
Component: Browser-General → Networking-Core
OS: Mac System 8.0 → Solaris
QA Contact: leger → mcafee
Hardware: PC → Sun
Updating OS/Platform info.
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
Target Milestone: M14 → M20
This is still technically a problem, but no one
seems to be hitting it right now.  m20.
Ok, off the radar.  marking won't fix.
Status: NEW → RESOLVED
Closed: 24 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.