| Bug ID |
11269
|
| Summary |
Find Packet/Find Next finds only the first match in the packet
|
| Product |
Wireshark
|
| Version |
1.12.5
|
| Hardware |
x86-64
|
| OS |
Red Hat
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.12.5 (88174f6 from master)
Copyright 1998-2015 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 GLib 2.42.1, with libpcap, with libz 1.2.3, without
POSIX
capabilities, without libnl, without SMI, without c-ares, without ADNS, without
Lua, without Python, without GnuTLS, without Gcrypt, with MIT Kerberos, without
GeoIP.
Running on Linux 2.6.32-220.7.1.el6.x86_64, with locale en_US.UTF-8, with
libpcap version 1.7.2, with libz 1.2.3.
Intel(R) Xeon(R) CPU X3440 @ 2.53GHz
Built using gcc 4.4.7 20120313 (Red Hat 4.4.7-11).
--
When using "Find Packets" By "String" and Search In "Packet details" the first
occurrence in the packet is correctly found and highlighted.
But after "Find next" it continues searching from the next packet ignoring all
further matches in the current packet.
So Find always finds only the first match of the searched pattern in the
packet.
Currently it seems to be impossible to find all matches (and this is what we
need).
You are receiving this mail because:
- You are watching all bug changes.