Closed
Bug 695685
Opened 14 years ago
Closed 13 years ago
dump in JS modules/components goes to stderr and doesn't flush
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: ted, Assigned: ted)
Details
Attachments
(1 file)
1.07 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
If you call dump() in a JS module or component, it goes to stderr, and doesn't flush stderr. If you call dump() in a window context or a frame script, it goes to stdout and does flush stdout. This is crazy.
Comment 2•13 years ago
|
||
Comment on attachment 568044 [details] [diff] [review]
Make JS module/component dump go to stdout and flush
Review of attachment 568044 [details] [diff] [review]:
-----------------------------------------------------------------
Should Debug() go to stderr? Also, please use -p in your diffs for review!
Attachment #568044 -
Flags: review?(mrbkap) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Sorry about the diff, apparently I don't have -p in my options on my mac! Making Debug go to stderr doesn't sound unreasonable, but that's a lot more fiddly work than this patch, since right now Debug just calls Dump. I'm just going to push what I have for now, since this fixes a real problem that ahal hit with his harness.
http://hg.mozilla.org/integration/mozilla-inbound/rev/cb7af497e97a
Status: NEW → ASSIGNED
![]() |
||
Comment 4•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
You need to log in
before you can comment on or make changes to this bug.
Description
•