Closed Bug 3839 Opened 26 years ago Closed 26 years ago

In DOS window, "short circut" should read "short circuit"

Categories

(Core Graveyard :: Tracking, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cpratt, Assigned: shaver)

Details

Attachments

(2 files)

If you watch the messages scroll by in the DOS window that apprunner creates, you will eventually see a message that reads "short circut". This (presumably) should read "short circuit". This is of course probably the most inconsequential bug I can possibly think of, but hey, I thought I'd document it just in case this goes out to customers.
Target Milestone: M5
Changed target milestone to M5.
QA Contact: 3853
Target Milestone: M5 → M6
Changed target milestone to M6.
Assignee: don → law
Target Milestone: M6 → M7
Assigned to law for M7.
Assignee: law → shaver
Status: ASSIGNED → NEW
Law's got lots of M7 bugs, so I'll take this one off his plate.
This was limiting our ability to back-load and was also costing us loopling performance, so I've committed a fix for the output issue. (Left comment intact, just because.) Output is also marked DEBUG_danm, it seems.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
It looks to me almost as if there is no QA Contact for this bug, either... Is this correct?? What happens then??
QA Contact: cpratt
If there's no QA contact assigned, I believe the proper protocol is to assign it to the default QA contact for the area, or to the reporter if s/he is a QA engineer (which cpratt is). So, I'm assigning myself as the QA Contact. OTOH I haven't seen the "short circuit" thingy pop up in the DOS box lately. So... if you'd please be so kind as to verify this fixed, I'd very much appreciate it, zuperdee. Thanks!
I have a feeling the message no longer pops up either... As Shaver rightly points out, the code that produces that output was #ifdef DEBUG_danm, so my guess would be that since the time you saw it, this code has since been disabled... If so, then should we try enabling it temporarily and seeing if it produces the correct output? Otherwise, I'd say that this statement clearly indicates that danm@netscape.com was the guilty party that wrote this code in the first place, so maybe we should ask him?
Status: RESOLVED → VERIFIED
well heck, if it was debug code causing this, I'm closing this out as it's way too trivial to show up on our bug radar. :) thanks!
Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.
bulk reassigning all bugs from shaver's @netscape account to his @mozill acount
Status: RESOLVED → VERIFIED
Presumed fixed. :)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: