Bug ID |
9130
|
Summary |
Crash if wrong "packet lengths range" entered
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.1
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Version 1.10.1 (SVN Rev 50926 from /trunk-1.10)
Compiled (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jul 26 2013), with AirPcap.
Running on 32-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 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, with 3070MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Edit > Preferences > Statistics > Stats Tree > Packet lengths
create (a edit) a entry. Type a single number (64 for example) or just put
there a "space".
Then start to capture packets and run Statistics > Packet lenghts... without
filters.
Program crashes and closes.
It's a pity that I can't to see percent of packet's with exact size, not a
range (64-64 doesn't work too).
You are receiving this mail because:
- You are watching all bug changes.