Comment # 7
on bug 7755
from Chris Maynard
(In reply to comment #6)
> 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.
I've still been compiling Wireshark with epan/packet.c's
dissector_add_uint_sanity_check() running. With "Open a console window" set to
either "Automatic" or "Always", when I run Wireshark from cmd.exe, I get:
16:26:50 Warn tcp.port: http registering using pattern 3689 already
reg
istered by http
16:26:50 Warn sctp.port: ssl registering using pattern 443 already
regi
stered by ssl
16:26:50 Warn tcp.port: uma registering using pattern 14001 already
reg
istered by uma
... but when it's set to "Never", then no output is generated. Results differ
when run from cygwin though. With cygwin, lots more output is generated
regardless of the setting.
> So what is the purpose of options for popping up a console window other than
> "Automatic"?
Good point. I don't know why "Always" is needed.
You are receiving this mail because:
- You are watching all bug changes.