Wireshark-bugs: [Wireshark-bugs] [Bug 9130] Crash if wrong "packet lengths range" entered
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 12 Nov 2013 14:50:59 +0000

Comment # 5 on bug 9130 from 
Thank you for the reply. We are using version 1.11 pulled from the git hub
repository on September 17th.  

The exact procedure we used to cause the crash was as follows:
-Add a new range of 64-64 (or 64 stored)
-Move that 64 range up to the top spot on the list
-Start a live capture
-Go to Statistics >> Packet Length
-Click Create Stat
and the program crashes.
We've replicated it with the '64' range in the second and third spots, as well.

Since the single range is supported, we will look for the cause of the crash
downstream from the range input box.  We will look into the call to use the
ranges instead.  

The reason for thinking the ranges needed to be in a certain order was that if
the '64' range was at the start, no other ranges would have any percentage
following that range; and maybe that was causing the crash.

Thanks again for the help.

You are receiving this mail because:
  • You are watching all bug changes.