https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9112
--- Comment #6 from doh <ncrdy7wf@xxxxxxxxxx> ---
Thanks for formatting!
I think that this bug came to life after the gulong -> guint32 switch done in:
http://anonsvn.wireshark.org/viewvc/trunk/epan/follow.c?r1=46402&r2=46748
About http://anonsvn.wireshark.org/viewvc?view=revision&revision=31334,
I see here the meaning of changing the curly bracket's location, but yes dont
understand the reason of the other line's glongcasting/subtraction instead of
previous single '>' operator..
Maybe Sake can answer?
What I know is that, after applying my patch, I've never seen again incorrect
"bytes missing in capture file" msgs, and all data are ok
[I use tshark/wireshark mainly for decoding http streams, and I've done by
myself the dechunk/gunzip routines, since I've seen they were broken in
wireshark].
If I'll have time, I'll anonymize some capture files that show the issue.
--
You are receiving this mail because:
You are watching all bug changes.
