Wireshark-bugs: [Wireshark-bugs] [Bug 10428] tshark's -c flag no longer operates correctly
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 27 Aug 2014 17:14:36 +0000

Comment # 1 on bug 10428 from 
After researching a little more, it appears this change went in as commit:
5c851858d9d64c6f24a970ea0c8b1cbcc6786df0.

In the log for that commit, the author suggested using -2 and -R combined with
-c to limit the packet count.  That does produce the 3-packets of output, but
with the negative side-effect that the packets are renumbered 1,2,3 in that
output, thus making it impossible to correlate back to the original frame
numbers in the file as a whole.

There is more discussion in bug 9048.

The should still be a way to limit the output by a count, independent of a
reading limit on input.

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