93647 - Give me former console output on PR_LOG

Status: VERIFIED DUPLICATE of bug 76720

(SeaMonkey :: Build Config, defect)

Description

[Ben Bucksch (:BenB)]

I need a way to get former console messages (removed with bug 76720).

Console output of errors and important status messages give invalueable hints
for debugging of arbitary bugs that I run into during using/constomizing
Mozilla. The console output has been removed, with the argument that I can use
PR_LOG. That's OK, but I can't get it to work.

But Dauphin said, these outputs were just |ifdef DEBUG|ed, not moved to PR_LOG.

If that's wrong, I'd like to know, what I need to set NSPR_LOG_MODULES to. I
tried "all:1" to "all:5", and on all detail levels, I get spammed by
nsComponentManager:CreateInstances etc. - 1.3 MB for startup of a single browser
window. I cannot set the module to a specific one, because I often don't know,
what component is at fault, and some errors are not reproducable (for changing
the env var, I need to restart Mozilla).

I use non-debug, optimized builds, and won't stop doing so. "debug" produces
major bloat during compilation (~3 times as large object files), and "debug,
non-optimized" produces considerably slowlier code.

Note that I need both former C++-printf()s and JS-dump()s.

Comment 1

[cls]

The original bug on this subject has not been closed.  Marking dupe.


*** This bug has been marked as a duplicate of 76720 ***

Comment 2

[Jon Granrose]

verified.