Closed
Bug 297027
Opened 20 years ago
Closed 20 years ago
NS_ScriptErrorReporter(JSContext *cx, const char *message, JSErrorReport *report) doesn't report message to stdout
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: timeless, Assigned: timeless)
Details
Attachments
(1 obsolete file)
It took me a really long time to figure this one out. I can provide a stack
trace if people care, but basically fairly often report->ucmessage is not filled
in, although message is, which means if you want to see the message because the
console error reporter won't show it to you, you'll be fairly disappointed by
the console output.
Assignee: general → timeless
Status: NEW → ASSIGNED
Attachment #185635 -
Flags: superreview?(jst)
Attachment #185635 -
Flags: review?(jst)
|
||
Comment 2•20 years ago
|
||
Comment on attachment 185635 [details] [diff] [review]
report ascii message when ucmessage isn't provided
r+sr=jst
Attachment #185635 -
Flags: superreview?(jst)
Attachment #185635 -
Flags: superreview+
Attachment #185635 -
Flags: review?(jst)
Attachment #185635 -
Flags: review+
Attachment #185635 -
Flags: approval1.8b3?
|
||
Comment 3•20 years ago
|
||
Comment on attachment 185635 [details] [diff] [review]
report ascii message when ucmessage isn't provided
a=chofmann
Attachment #185635 -
Flags: approval1.8b3? → approval1.8b3+
Comment on attachment 185635 [details] [diff] [review]
report ascii message when ucmessage isn't provided
mozilla/dom/src/base/nsJSEnvironment.cpp 1.255
Attachment #185635 -
Attachment is obsolete: true
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•