http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1190
------- Comment #5 from ulf.lamping@xxxxxx 2007-11-14 07:26 GMT -------
Well, I've fixed all appearances of the problem in the Wireshark code, but as
with my last comment, the zlib problem still remains.
zlib uses the "long" data type for file offsets, so any build system that uses
"long" as being 32 bits (most 32 bit operating systems?) will still suffer from
that 2GB problem.
Wireshark needs this offset for "random file access" and will show garbage in
packets located behind the 2GB border of the file. tshark doesn't suffer from
this problem - it's only sequentially reading the file so this offset is not
required.
Unless zlib addresses this problem or we replace zlib with something different,
this problem remains ...
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
