ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-users: Re: [Wireshark-users] Errors in tshark

From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
Date: Wed, 25 Sep 2013 21:31:08 +0200
Le 25/09/2013 20:37, Kurt Buff a �crit :
> All,
>
> Was filtering a 1gb capture file looking for STP packets, and got some errors.
>
> I got the output I was looking for, I believe, but wanted to report
> back to the community, in case it's an issue that needs to be
> addressed.
>
> Running this on Win7 x64 Enterprise. Wireshark 1.10.2
>
> I had merged a bunch (~200 @5mbytes each) of smaller capture files and
> then performed the following, with the results shown. I did some quick
> googling, and found reports of similar errors, so it's entirely
> possible that someone's already working on it - if so, feel free to
> ignore this message.
>
> C:\PacketCaptures\dump>"C:\Program Files\Wireshark\tshark" -r
> 0901.pcap -Y stp -w c:\packetcaptures\stp.pcap
>
> * (tshark.exe:6508): WARNING **: Too many taps queued
>
> * (tshark.exe:6508): WARNING **: Too many taps queued
>
> * (tshark.exe:6508): WARNING **: Too many taps queued
>
> * (tshark.exe:6508): WARNING **: Too many taps queued
>
> * (tshark.exe:6508): WARNING **: Too many taps queued
>
> * (tshark.exe:6508): WARNING **: Dissector bug, protocol TDS, in
> packet 820830: proto.c:4246: failed assertion "end >= fi->start"
>
>
> If someone needs more info, I will do my best to oblige.
Hi Kurt,
could you fill a bug on http://bugs.wireshark.org with a pcap file that
contains packet 820830 of your capture (the one triggering the dissector
bug) so that we can have a look at it and fix the bug?

Thanks a lot,
Pascal.