http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1190
------- Comment #3 from ulf.lamping@xxxxxx 2006-11-05 23:19 GMT -------
ok, it's a "long" in the code not an "int" (as I've written in the previous
comment - but this in effect is the same on the platforms we use).
I've replaced all long's by gint64 so the code in Wireshark itself should be
clean now. Unfortunately, we're using zlib to access the capture file, which is
not able to handle 64bit offsets.
So you can build a Win32 version without zlib yourself or wait until we've
fixed the remaining zlib issue.
BTW: I'm pretty sure now, if you see strange values in the status bar you'll
certainly get a strange packet list display (for packets > 2GB) as well.
--
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.