[Vm-dev] Reproducible crashing the VM with a zipped fuel serialization

[Mariano Martinez Peck]

On Wed, Jan 17, 2018 at 6:41 PM, Max Leske <maxleske at gmail.com> wrote:

>
> Hi Mariano,
>
> The archive is in Zip64 format. The Zip format documentation (
> https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT) states:
>
>
Hi Max,


thanks for the pointer. So what you are saying is the generated zip that
github offers for downloading is a Zip64 bit format because otherwise it
would haven't fit in the regular 32, right?
And of course, then we don't have Zip64 support.

Is that it?





>  4.4.21 total number of entries in the central dir on
>           this disk: (2 bytes)
>
>       The number of central directory entries on this disk.
>       If an archive is in ZIP64 format and the value in
>       this field is 0xFFFF, the size will be in the
>       corresponding 8 byte zip64 end of central
>       directory field.
>
> That's exactly what I see, when I look at the data extracted from the
> central directory. As was pointed out, the implementation in Pharo doesn't
> support Zip64, although it would be nice to have.
>
> Cheers,
> Max
>
>
>
> On 16 January 2018 at 07:40:05, Max Leske (maxleske at gmail.com) wrote:
>
> Hi Mariano,
>
> I'll check that.
>
> On 14 January 2018 at 21:10:17, vm-dev-request at lists.squeakfoundation.org
> (vm-dev-request at lists.squeakfoundation.org) wrote:
>
> Hi Max,
>
> Great debugging capabilities! Since you are already in deep waters....could
> you check if it's the same problem I reported in the email "Problem with
> ZipArchive (probably bug due to large file)"?
>
> Thanks a lot in advance,
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180118/b3f15644/attachment.html>