https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15467
Bug ID: 15467
Summary: Some Wireshark command-line options don't work and
generate QWaitCondition warnings.
Product: Wireshark
Version: 2.6.6
Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
Severity: Normal
Priority: Low
Component: Qt UI
Assignee: bugzilla-ad...@wireshark.org
Reporter: christopher.mayn...@igt.com
Target Milestone: ---
Build Information:
Wireshark 2.6.6 (v2.6.6)
Compiled (64-bit) with Qt 5.12.0, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with MaxMind DB resolver, with
nghttp2 1.14.0, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia,
with AirPcap, with SBC, with SpanDSP, with bcg729.
Running on 64-bit Windows 10, build 17763, with Intel(R) Xeon(R) CPU E3-1505M
v5
@ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with locale
English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version
1.8.1, with GnuTLS 3.4.11, with Gcrypt 1.7.6, with AirPcap 4.1.3 build 3348,
binary plugins supported (0 loaded).
Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730).
The same problem exists in master as well:
Version 2.9.1 (v2.9.1rc0-576-g1260f3ed)
Compiled (64-bit) with Qt 5.12.0, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729.
Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Xeon(R) CPU
E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with
locale English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with AirPcap 4.1.0 build
1622, binary plugins supported (14 loaded).
Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730).
--
When running Wireshark from the command-line with certain Wireshark options
specified, not only do they not work, as mentioned in bug 14215, but they also
produce warnings of the following form:
09:47:03.802 Main Warn QWaitCondition: Destroyed while threads are still
waiting
There appears to be one such warning printed for nearly every non-extcap
interface. My system has 8 such interfaces and 7 warnings are printed.
The commands tested that not only fail but generate the warnings are:
1) wireshark -L
2) wireshark --list-time-stamp-types
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
