Closed Bug 300962 Opened 19 years ago Closed 15 years ago

-console doesn't work from cygwin bash

Categories

(Core Graveyard :: Cmd-line Features, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: BenB, Unassigned)

Details

Reproduction:
1. Open cygwin bash
2. There, start Mozilla using |mozilla.exe -console|
3. Open Windows commandline (cmd.exe)
4. There, start Mozilla using |mozilla.exe -console|

Expected result:
No difference between step 2 and 4.

Actual result:
Step 4 works (you see "stdout redirected..." and dump statements, if enabled in
prefs)
Step 2 doesn't work: It opens a new console window, but you never see any
contents in it.
Huh, this is extremely annoying. I just spend quite some time trying to reproduce some exception dumps to the console some Linux guy claimed were there...
This is for sure a major flaw for Cygwin based hackers.
Severity: normal → major
Yeah, FYI, this probably costed me a full working day all in all until I realized what the cause was that I don't see dump()s. This is something I simply didn't think of as possible cause.
Not sure what's going on here, but I'm pretty sure it's a bug in the shell, not in Firefox, so I don't think there's anything else to do here.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
bsmedmerg, note that starting Mozilla from cygwin bash opens a new (cmd.exe-like) window with console (but dump() statements never end up there), but starting Mozilla from cmd.exe-console IIRC prints dump() statments directly in the original console. So, this may very well be a Mozilla bug.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
I still don't care... it's not worth fixing.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.