https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6256
Summary: Running "wireshark -i <interface> -c 100 -k -Q -w -"
from the command-line causes Wireshark to crash.
Product: Wireshark
Version: SVN
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: christopher.maynard@xxxxxxxxx
Build Information:
TShark 1.7.0 (SVN Rev 38675 from /trunk)
Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (32-bit) with GLib 2.26.1, with WinPcap (version unknown), with libz
1.2.5, without POSIX capabilities, with threads support, without libpcre, with
SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, with Python 2.7.2, with GnuTLS
2.10.3, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008).
Built using Microsoft Visual C++ 9.0 build 30729
--
As the summary indicates, running "wireshark -i <interface> -c 100 -k -Q -w -"
from the command-line causes Wireshark to crash.
Additionally, as reported by Guy here[1], there appears to be a related problem
running this command on Mac OS X. Apparently it doesn't crash but instead,
<quote>it popped up a complaint that "-" isn't a regular file (even though I'd
redirected the standard output to a file), but spewed out a ton of "poll(2)
failed due to: Bad file descriptor" complaints.</quote>.
[1] http://ask.wireshark.org/questions/5800/wireshark-from-command-line.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
