Use of read filter (-R) with Wireshark (or tshark along with the -2 option) presents inconsistent frame number references
This issue was migrated from bug 12792 in our old bug tracker.
Original bug information:
Reporter: Derek Felson
Status: CONFIRMED
Product: Wireshark
Component: TShark
OS: Linux
Platform: x86-64
Version: 2.2.0
Attachments:
broken-reduced.pcap: pcap for reproducing the bug
valgrind-output.txt: valgrind output
backtrace.txt: gdb backtrace