Wireshark-dev: Re: [Wireshark-dev] 1.12.0rc2 : tshark crash when message is on 3 packets
From: Pascal Quantin <[email protected]>
Date: Wed, 18 Jun 2014 00:41:38 +0200
2014-06-18 0:11 GMT+02:00 Pascal Quantin <[email protected]>:
2014-06-16 22:44 GMT+02:00 wsgd <[email protected]>:


My protocol (only to test this problem) specifications :
tcp port 20640
message is 5 bytes long

command line : tshark -r pb.cap  -T text -V
--> crash (see pb.1.12.0.txt)
ERROR:print.c:838:get_field_data: code should not be reached

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

wireshark does not crash and display is ok
tshark 1.10.6 does not crash and display is ok (see pb.1.10.6.txt)

Plugin dissector code is into packet-tcp-5-bytes.c


Hi Olivier,

thanks for the report.
This is a regression introduced by g21e0a63b2 commit for bug 9169. I proposed a fix (not calling the data dissector when a subdissector claims that the current TCP fragment needs more desegmentation) here: https://code.wireshark.org/review/2350


Hi Olivier,

as Evan noted in the review of my patch, the data dissector should not even be called as your dissector accepted the packet. It appears that there is a small bug in your current code. In function dissect_tcp_5_bytes(), replacing the line 30:
            return  offset;
            return  offset + available;
does not trigger the crash.

With the previous code, your dissector was returning the value 0 for frame 4, like if the packet was rejected. But at the same time you were considering the packet as acceptable and changing the pinfo->desegment_len, leading to an inconsistent state that should have been caught by a missing check in packet-tcp.c