 | 1 | initial version |
Wireshark doesn't use tshark. Both Wireshark and tshark use dumpcap.
Unfortunately, not only has Wireshark 2.4.0 has gone EOL as of July 19, 2019 per the Wireshark Lifecycle, but without being able to examine the dissector itself causing the problem, it will be very unlikely if not impossible for anyone to be able to help troubleshoot the problem you're experiencing. If you can provide the source code of the dissector and a sample capture file to test it with that causes the crash, then perhaps someone will be able to assist you then, although this isn't the best forum for that. Likely a discussion on the wireshark-dev mailing list would be a more suitable place.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
