https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4955
--- Comment #21 from Guy Harris <guy@xxxxxxxxxxxx> 2012-05-17 22:18:07 PDT ---
Wireshark 1.6 and later don't use the painful gzio routines to read gzipped
files - they have their own code to read them, using lower-level zlib routines
to do the decompression. One benefit is that they can save the dictionary
state at various points in the reading process, so that random access to the
gzipped file doesn't involve either scanning forward through the file if you're
seeking forward or rewinding the file and scanning forward to the new point if
you're seeking backward. Another benefit is that we don't get bitten by all
the unbelievable wonderfulness of zlib's handling of the file offsets depending
on the size of off_t and on whether you have 64-bit file offsets blah balh blah
blah.
Does this still happen with 1.6 or later? If not, we'll close this as fixed (a
lack of a response after some amount of time will be treated as "it's fixed").
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.