Don't look at packet or byte limits during the second pass of two-pass analysis.
authoreapache <eapache@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 22 Aug 2013 02:19:22 +0000 (02:19 +0000)
committereapache <eapache@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 22 Aug 2013 02:19:22 +0000 (02:19 +0000)
commitfdd9d5e27c6d7f8b53370544cd58610ee43f9d45
tree0ff4421dada9dc9bbd1509be27c895cb476c91ce
parent722f536e811178d7b1f02008fee79870dbfc2cf7
Don't look at packet or byte limits during the second pass of two-pass analysis.
The limits are enforced during the first pass, and frames that get dropped from
the first pass for this reason aren't available to the second pass at all, so
checking again is redundant.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@51460 f5534014-38df-0310-8fa8-9805f1628bb7
tshark.c