Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9130] Crash if wrong "packet lengths range" entered

[bugzilla-daemon@xxxxxxxxxxxxx]

Michael Mann changed bug 9130

What	Removed	Added
Status	CONFIRMED	RESOLVED
CC		mmann78@netscape.net
Resolution	---	FIXED

Comment # 1 on bug 9130 from Michael Mann

Fixed the crash in r52679 by preventing "invalid" ranges (like an empty string)
to be entered in the Packet Length dialog.  Scheduled for backporting to 1.10

Range of "64" now works, but even "64-64" should have worked before, it's just
a matter of order.  It appears a packet can only fit into a single range, so if
you have a range of 21-70, and then a range of 64-64, the packet will fall in
the "21-70" bucket.  If the 64-64 range is before 21-70 in the packet length
list, the packet will count in the 64-64 bucket and not be included in the
21-70 count.

---

      You are receiving this mail because:

• You are watching all bug changes.