| Bug ID |
10161
|
| Summary |
seems like hex matches are broken completely for frame and data
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.7
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.11.3 (v1.11.3-0-g1dd5d3a from master)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
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.1.1 with GLib 2.34.1, with WinPcap (4_1_3), with
libz 1.2.5, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, without
PortAudio, with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap, GnuTLS
2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, with 16060MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
1) Basic hex doesn't seem to work with regards to matching for certain hex
numbers. For example do a data.data matches "\x29" or frame matches "\x28".
The _expression_ immediately turns red.
2) Furthermore the regex doesn't seem to work even when you use hex digits that
don't turn red. Try to match a packet that has for example "\x4c......\x30"
(six anything bytes between 4c and 30) and it fails to match.
Tried the stable 1.10.7 and now the dev version both seem to have the problem.
You are receiving this mail because:
- You are watching all bug changes.