Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 11187] New: abnormal behavior for display filter auto-completion

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	11187
Summary	abnormal behavior for display filter auto-completion
Product	Wireshark
Version	1.99.x (Experimental)
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Qt UI
Assignee	bugzilla-admin@wireshark.org
Reporter	xiaochsu@foxmail.com

Created attachment 13602 [details]
display filter auto-completion/history

Build Information:
Version 1.99.6 (v1.99.6rc0-499-gf563695 from unknown)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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 (32-bit) with Qt 5.4.0, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.38.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, without PortAudio,
with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz (with SSE4.2), with 2991MB of
physical memory.

Built using Microsoft Visual C++ 12.0 build 21005
--
It seems there is conflict between display filter history and auto-completion.
For example, If there is already a display history of "qct.logcode == 0xB0C0",
when we input qct.logcod and select display filter history "qct.logcode ==
0xB0C0", the result is "qct.logcode == qct.logcode == 0xB0C0".

---

      You are receiving this mail because:

• You are watching all bug changes.