| Bug ID |
11946
|
| Summary |
Display Filter Macros no longer identified after creating new display filter macro.
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
CONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14189 [details]
screenshot showing the error message and the existence of the filter
Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (with SSE4.2), with 16374MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 31101
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Open Wireshark and open a capture file.
Apply a previously existing display filter macro ${example}
Clear the display filter macro from the filter bar.
Open Analyze->Display Filter Macros, create a new macro ${new} and click [OK].
Attempt to apply ${new} or ${example} and get Invalid filter: macro 'example'
or 'new' does not exist.
Open Analyze->Display Filter Macros and the macros exist.
Exit and re-open Wireshark and capture file,then re-apply the macros and they
work.
You are receiving this mail because:
- You are watching all bug changes.