Re: [Wireshark-dev] Tshark closing unexpectedly due to failure reading from file

Hi, From the issue report I saw that you’re using some development version “TShark (Wireshark) 3.1.0 (v3.1.0rc0-268-g09a04829)”. Can’t say it makes a difference in this case, but this is not recommended. If you could update to the latest 3.2, or 3.4 release that would at least give us some stab

Re: [Wireshark-dev] Tshark closing unexpectedly due to failure reading from file

On Nov 18, 2020, at 4:25 PM, James Ko wrote: > I've been helping Alastair debug this problem and this is as far as we got. > I can only think of a race condition between dumpcap completing the packet > writing to the file and tshark being able to read the expected number of new > packets. > >

[Wireshark-dev] Windows build - all_guides fails on .chm files

New Windows 10 build system so might be due to tool versions. Any tips on how to diagnose this? "The build of 'C:\Development\wsbuild64\CMakeFiles\470a6095470174e9ce53bf13b7d8b057\developer_guide_chm.rule' depends on 'C:\DEVELOPMENT\WSBUILD64\DOCBOOK\DEVELOPER-GUIDE.CHM' which is produced by

Re: [Wireshark-dev] Tshark closing unexpectedly due to failure reading from file

I've been helping Alastair debug this problem and this is as far as we got. I can only think of a race condition between dumpcap completing the packet writing to the file and tshark being able to read the expected number of new packets. I do see there is fflush() in capture_loop_write_pcapng_cb()