Closed
Bug 78663
Opened 24 years ago
Closed 23 years ago
[console] qt port should not print to console in opt builds
Categories
(Core :: XUL, defect, P2)
Core
XUL
Tracking
()
RESOLVED
FIXED
mozilla0.9.5
People
(Reporter: cls, Assigned: johng)
References
Details
Attachments
(1 file)
(deleted),
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>
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.
Assignee | ||
Comment 3•24 years ago
|
||
This patch looks fine to me, but the file (nsFontRetrieverService.cpp) is not
currently included in the Qt build, so applying it results in no net change to
the actual application. If you want, we can apply it anyway to prevent this
issue from coming up again in the future. Please let me know how you wish to
proceed.
r=johng@corel.com
Comment 5•24 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.
Target Milestone: mozilla1.0 → mozilla0.9.2
Assignee | ||
Comment 6•24 years ago
|
||
Adding my home email as a CC, since today is my last day at Corel.
Comment 7•24 years ago
|
||
I'll re-iterate my r=, with my new address:
r=jcgriggs@sympatico.ca
Comment 8•24 years ago
|
||
I have commited the patch to CVS.
Comment 9•24 years ago
|
||
pushing out. 0.9.2 is done. (querying for this string will get you the list of
the 0.9.2 bugs I moved to 0.9.3)
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Comment 11•24 years ago
|
||
I thought I had checked in code that removed the offending printfs already, but
doulbe-checking today, I find I had not. This is fixed as of today.
Comment 12•23 years ago
|
||
Patches for this are now in CVS, so I am marking this FIXED. Please open a new
bug report for any remaining problems, assigned to jcgriggs@sympatico.ca (the
Corel address is no longer valid).
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 13•23 years ago
|
||
moved to milestone 0.9.5, 0.9.4 is over. per pdt mtg.
Target Milestone: mozilla0.9.4 → mozilla0.9.5
You need to log in
before you can comment on or make changes to this bug.
Description
•