Closed
Bug 223651
Opened 21 years ago
Closed 21 years ago
mozilla-1.6a/plugins/libnullplugin.so returned 1402ea490
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: mmokrejs, Assigned: peterlubczynski-bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030826
Build Identifier: nightly snapshot from yeaterday
Hi,
I'm getting on startup on Tru64Unix the following message:
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp,
line 3188
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp,
line 3188
GFX: dpi=75 t2p=0.0526316 p2t=19 depth=24
WEBSHELL+ = 1
LoadPlugin() /afs/.gsf.de/@sys/usr/lib/mozilla-1.6a/plugins/libnullplugin.so
returned 1402ea490
GetMIMEDescription() returned "*:.*:All types"
What does that mean?
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
![]() |
||
Comment 1•21 years ago
|
||
That's just the return code from the function. You're running a debug build, so
you're getting all sorts of debugging output... To someone trying to debug a
plugin problem, that return code could be useful.
Marking invalid, since there's no bug here.
![]() |
||
Comment 2•21 years ago
|
||
.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•21 years ago
|
||
But the output be labeled with "Debug: " in front of the line?
![]() |
||
Comment 4•21 years ago
|
||
No. All the output you see there is debug output. In non-debug builds,
Mozilla itself should not print anything to stdout. If it does, _that_'s a bug.
Reporter | ||
Comment 5•21 years ago
|
||
Yes, you might be right, but in this "debug" output there's somewhere an error,
and it terribly difficult to find that. Look for Tru64Unix bugs and you will see
what I mean. Labelling debug lines with "Debug:" does not hurt, right? :)
since *all* lines are debug output, labeling *all* lines with Debug: would not help, and having to do it would hurt (plus it'd break our tests).
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•