You would be correct, it's a loop over a tapping point. Logged bug 7845 and CCed the original author just because the specs aren't free. Probably a trivial fix though.
-----Original Message----- From: Jaap Keuter <jaap.keu...@xs4all.nl> To: Developer support list for Wireshark <wireshark-dev@wireshark.org> Sent: Wed, Oct 10, 2012 5:30 pm Subject: Re: [Wireshark-dev] WARNING **: Too many taps queued On 10/10/2012 03:48 PM, mman...@netscape.net wrote: > I ran some fuzztesting overnight (on a 32-bit WinXP VM, off of trunk), and when > I checked on it this morning, I had "WARNING **: Too many taps queued" so many > times, it scrolled beyond the top of my window. > > I've never seen this before. Could it be a result of the files I was testing? > New bug in the trunk? > > Any insight would be appreciated. > Your fuzz probably triggered a loop over a tapping point. There can be TAP_PACKET_QUEUE_LEN (=100) taps be pushed per packet. You should grab that fuzz and investigate the loop. Thanks, Jaap ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
