Closed
Bug 78664
Opened 25 years ago
Closed 25 years ago
[console] Windows widgets must not print to console in opt builds
Categories
(Core :: XUL, defect, P4)
Tracking
()
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: cls, Assigned: dr)
References
Details
(Whiteboard: [wanted for mozilla0.9.2])
Attachments
(3 files)
|
3.20 KB,
patch
|
Details | Diff | Splinter Review | |
|
13.57 KB,
patch
|
Details | Diff | Splinter Review | |
|
13.56 KB,
patch
|
Details | Diff | Splinter Review |
<formletter>It has been decreed (or requested at any rate) that our release
(read non-debug) builds must not print anything to the console when the app is
running. See bug 76720 for details. I have done a preliminary tree scouring
and created mini-patches for each module that has bare printfs. These patches
are not all inclusive as I didn't even think about xul/js output until post
scour so module owners & peers will still need to scour their modules themselves
as well as make sure the preliminary patches do not break anything.</formletter>
Comment 2•25 years ago
|
||
There is no console in optimized win32 builds. (Although, there is an
undocumented '-console' switch).
Naked 'printf' in C++ is (for the most part) wrong, but a lot of bugs are
brought to an easy resolution simply by bug reporters reporting the error
messages that appear in the console. I think this is a mistake, if the
intent to disable any and all capability to get console output in optimized
builds.
Sorry about the additional spammage but I should clear up a couple of things
before everyone starts replying.
1) I'm just the messenger. Discussions outside of the specific module/patches
should be discussed in the parent bug ( bug 76720).
2) I have no intention of checking in the patches as is; that's why the bugs are
assigned to someone else ;).
3) The patches are the result of a far & wide-reaching grep across the entire
tree. They may affect some cases that are not even used and they are far from
optimal.
4) Some platforms/ports will not need the printfs shutoff as they use other
mechanisms to stop the printfs. That's fine. Note it in the bug and close it
as invalid(?). Depending upon the platform/port some people may still be
interested in removing the overhead from the printfs.
Status: NEW → ASSIGNED
Priority: P2 → P4
Summary: [console] windows widgets must not print to console in opt builds → Windows widgets must not print to console in opt builds
Updated•25 years ago
|
Summary: Windows widgets must not print to console in opt builds → [console] Windows widgets must not print to console in opt builds
Comment 6•25 years ago
|
||
lets keep dribbling these [console] bugs into the tree as quick as we
can, but they shouldn't hold up or block 0.9.1 so moving the target milestone
to 0.9.2.
Comment 9•25 years ago
|
||
r=jag
Comment 10•25 years ago
|
||
sr=hyatt
| Assignee | ||
Comment 11•25 years ago
|
||
cc'ing Brendan per trudelle's recommendation. drivers@mozilla.org hasn't
reponded since I sent a request for a= last Thursday (6/14). Looking for a quick
a= before we close for 0.9.2.
a=dbaron for trunk checkin (on behalf of (some of) drivers)
| Assignee | ||
Comment 13•25 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 14•25 years ago
|
||
couple of straggling messages from outside windows widgets, but that's a
separate matter. Ka-chunk!.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•