Closed Bug 203615 Opened 22 years ago Closed 19 years ago

NS_PRECONDITION: Truth in advertising (1)

Categories

(Core :: XPCOM, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: bfowler, Assigned: dougt)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030418 Chimera/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030418 Chimera/0.7+ NS_PRECONDITION resolves to call of Assertion( ) (see line 430 of nsDebug.cpp). This seems curious. I would have thought that a separate function was needed. to indicate that it was a precondition that was not met. Reproducible: Always Steps to Reproduce: 1. Mess up a function call so that its preconditions are not met 2. Watch the log 3. Actual Results: Missing pre-condtions are logged as assertion failures Expected Results: The two types of inconsistency are different and should be logged separately
nothing to do with camino
nothing to do with camino
Assignee: saari → dougt
Component: General → XPCOM
Product: Camino → Browser
QA Contact: winnie → scc
Version: unspecified → Trunk
You can close the bug as INVALID if you wish. What it has to do with Camino is that it is a DOGFOOD issue, that is, it is an incongruity in the code which intereferes with debugging. If you don't think that it is invalid, then it should go to Mozilla, but as I only work on Camino, I am not going to do that.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.