Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 6256] Running "wireshark -i <interface> -c 100 -k -Q -w -" from the command-li

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6256

--- Comment #3 from Guy Harris <guy@xxxxxxxxxxxx> 2011-08-23 16:38:33 PDT ---
The good news: on OS X, the command in question just quits, without any error
spamming.

The bad news: Wireshark just quits immediately, taking down whatever dialog box
it popped up.

The other news: I haven't tried it on Windows yet. :-)

The good news qualifies that as an improvement.  The bad news means it should
either print an error to the standard error before exiting ("-k" means you're
probably running it from the command line, so you'll probably see the error,
although there might be something that fires it up from the GUI - on OS X, the
standard output and error of a GUI session is snarfed by /dev/console in older
releases and piped to launchd in newer releases, so the errors will show up in
a log file displayed by Console, but other UN*Xes might send the standard
output and error to /dev/null, and Windows would require popping up a console),
or should pop up a dialog box and keep running.  I'm not sure what the right
answer would be.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.