Wireshark-bugs: [Wireshark-bugs] [Bug 10481] New: "Find Packet" by String, Packet list, does not
| Bug ID |
10481
|
| Summary |
"Find Packet" by String, Packet list, does not find the next packet.
|
| Product |
Wireshark
|
| Version |
1.12.1
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Common utilities (libwsutil)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
ggovier@shaw.ca
|
Created attachment 13066 [details]
about to click to search screen shot
Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> 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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, 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 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, with 8117MB 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.12.1 64bit
"Find Packet" by String, in Packet list, does not find the next packet after
finding the 1st one.
It's the same either using the menus or CTRL-N.
finding previous packet also doesn't work.
also, if I, for example, select packet 156 in the summary.
I do a find in direction down, I expect it to find the data in packet 157.
It goes back and finds it in packet 155 (the first occurrence).
As I record this I realize CTRL-N and CTRL-B always go to the 1st occurrence,
no matter what packet I start at.
Screen shot attached. (damn, it looks like I can only attach 1 screen shot.)
You are receiving this mail because:
- You are watching all bug changes.
