Wireshark-bugs: [Wireshark-bugs] [Bug 8609] Redirection of "wireshark.exe -D" to a text file is
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 24 Apr 2013 22:02:12 +0000

Comment # 6 on bug 8609 from 
(In reply to comment #5)
> Is that expected behaviour on Windows?

I'm not sure whether Wireshark is built for the "console subsystem" or the
"Windows subsystem" on Windows, but it probably *should* be built for the
"Windows subsystem", and that may mean that, by default, there's no console for
a process created that runs it, *even if it's run from the command line*.

The right fix may be to add "printf_stdout()" routines that, in Wireshark (but
*not* in TShark or dumpcap or any console-mode programs), creates a console if
we don't already have one, so that output to stdout, as well as output to
stderr, goes to a console.

BTW, I don't know whether the Windows shell (cmd.exe) supports 2> or not.  It
might not.

You are receiving this mail because:
  • You are watching all bug changes.