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

--- Comment #1 from Guy Harris <ghar...@sonic.net> ---
(In reply to allenmenor16 from comment #0)
> Build Information:
> 3.2.4 (v3.2.4-0-g893b5a5e1e3e)
> 
> Compiled (64-bit) with Qt 5.12.8, with WinPcap SDK (WpdPack) 4.1.2, with GLib
> 2.52.3, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.15.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.39.2, with brotli, with LZ4, with
> Zstandard, with Snappy, with libxml2 2.9.9, with QtMultimedia, with automatic
> updates using WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled
> resampler), with SBC, with SpanDSP, with bcg729.
> 
> Running on 64-bit Windows Server 2012R2, build 9600, with Intel(R) Xeon(R)
> CPU
> E5-2690 v4 @ 2.60GHz (with SSE4.2), with 8191 MB of physical memory, with
> locale
> English_United States.1252, with light display mode, without HiDPI, with
> Npcap
> version 0.9991, based on libpcap version 1.9.1, with GnuTLS 3.6.3, with
> Gcrypt
> 1.8.3, with brotli 1.0.2, without AirPcap, binary plugins supported (19
> loaded).
> 
> Built using Microsoft Visual Studio 2019 (VC++ 14.25, build 28614).
> 
> --
> When applying combined display filter macros, Wireshark crashes.
> 
> Steps to Reproduce:
> 1. In Analyze > Display Filter Macros, create a complex macro with macros 
>     separated by '&&' or '||'
> 
> For example, complex macro 'R4' has the following text ${R:$1} && ${4RS}0
> 
> 2. Apply the macro in 'Apply a display filter' bar typing in the complex
> macro 
>     'R4'
> 3. Press 'Enter' key and Wireshark crashes
> 
> Actual Results: Wireshark crashes.
> 
> Expected Results: Packet capture is parsed and filtered according to the
> macro 
>     with no interruptions/crash.
> 
> Additional Information/Problem Details: The macros I have been using no
> longer works in Wireshark versions 3.2.4 and above.

"No longer works in Wireshark versions 3.2.4 and above" meaning:

    The macros I have been using didn't crash, and worked, with packets being
filtered correctly, in Wireshark versions up to 3.2.3, and don't crash, but
don't work, with packets *not* being filtered correctly, in Wireshark 3.2.4 and
later versions?

    The macros I have been using didn't crash, and worked, with packets being
filtered correctly, in Wireshark versions up to 3.2.3, and crash in Wireshark
3.2.4 and later versions?

-- 
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

Reply via email to