Bug ID: 14427
Summary: Crash on `ip address1 22.214.171.124` filter
OS: Windows 10
Component: Dissection engine (libwireshark)
Target Milestone: ---
Version 2.4.4 (v2.4.4-0-g90a7be11a4)
Copyright 1998-2018 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
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 (64-bit) with Qt 5.6.3, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
SBC, with SpanDSP.
Running on 64-bit Windows 10, build 16299, with Intel(R) Core(TM) i7-6700HQ CPU
@ 2.60GHz (with SSE4.2), with 49087 MB of physical memory, with locale
Croatian_Croatia.1250, with WinPcap version 4.1.3 (packet.dll version
126.96.36.19980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.4.11, with Gcrypt 1.7.6, without AirPcap.
Built using Microsoft Visual C++ 14.0 build 24215
Wireshark is Open Source Software released under the GNU General Public
Check the man page and http://www.wireshark.org for more information.
If I try to enter a capture filter ``` Wireshark crashes as soon as I start
entering the IP address or paste it in.
Same happens with `tcp address1 188.8.131.52`.
The actual IP address used does not seem to be important.
I later on figured out I can filter by IPv4 address using `host 184.108.40.206`
and that one works fine.
The original tried queries were constructed based on what Wireshark offered in
its auto-completion popups.
You are receiving this mail because:
You are watching all bug changes.
Sent via: Wireshark-bugs mailing list <email@example.com>