Wireshark-bugs: [Wireshark-bugs] [Bug 7755] A console window is never opened.
Comment # 6
on bug 7755
from Guy Harris
(In reply to comment #5)
> (In reply to comment #4)
>
> > BTW, for developers, that works on Windows 7 if you create a shortcut to
> > wireshark-gtk2\Wireshark.exe and launch Wireshark from the shortcut, but it
> > still doesn't work if you run it from the command-line. I guess that is to
> > be expected though.
>
> Ah, but I see now that if you run it on the command-line, any output just
> gets displayed on the command-line so a new console isn't needed.
Yes - the code does, and has done that for a while:
attempt to attach to parent process's console;
if (that attempt fails)
attempt to open a new console;
The first attempt will succeed if you run Wireshark from cmd.exe. (If you run
it from a Cygwin prompt, the standard input, output, and error are set to pipes
to what I presume is the Cygwin terminal emulator program's process, and the
code now decides that there's no need to attach to a console and makes no
attempt to do so, leaving the standard handles un-redirected; output to those
pipes show up in the Cygwin terminal window.)
> Would it make sense to change the text from:
> Open a console window: Never | Automatic | Always
>
> to *something like*:
> Display debugging information: Never | Automatic | Always
Well, people might think "Display debugging information" being set to "Never"
would prevent debugging information from showing up even if you run Wireshark
from a console - and, given that, on Windows, Windows-subsystems applications,
which Wireshark is on Windows, will be run "in the background" when run from
cmd.exe, so the output could show up while something else is running, maybe it
*should* mean that.
So what is the purpose of options for popping up a console window other than
"Automatic"?
You are receiving this mail because:
- You are watching all bug changes.
