On 2023-10-05 11:41, ASSI via Cygwin wrote:
ASSI via Cygwin writes:
I could reproduce that issue, no time yet to dig deeper. It looks like
the decompressor loses track of where it is, then uses whatever data
comes after that to try and extract the next file (which obviously
doesn't look like it's expected to).
Both GNU tar and bsdtar (from libarchive) decompress the archive
correctly, so that would allow you to install manually. Looking at the
file that produces the failure, it is quite a bit larger than 2GiB, so I
think that this simply means that the canned tar extractor in setup.exe
is just not large-file safe.
I hadn't realised that file was so large when decompressed: that definitely
looks like a 32 bit signed overflow issue: changing the signed offset(s) or
size(s) to unsigned, or size_t if larger, should eliminate future issues.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
