[squeak-dev] Re: filesize reporting 0 for very large files

Andreas Raab andreas.raab at gmx.de
Fri Mar 16 08:53:56 UTC 2012


On 3/16/2012 5:45, David T. Lewis wrote:
> On Thu, Mar 15, 2012 at 10:35:47PM -0500, Chris Muller wrote:
>> I have a 3.2GB file, but Squeak reports its #fileSize as 0 (in the
>> DirectoryEntry).  It seems to occur for any file that large.
>>
>> Is it an overflow condition in the VM?  Is it possible to fix?
>
> It works fine with an interpreter VM compiled in 64-bit mode. I
> cannot look into it in detail now, but an educated guess is that
> it relates to the definition of size_t for 32-bit programs, and
> that for the kind of work you are doing here a 64-bit VM may be
> in order.

That shouldn't be necessary. The VMs have long been updated to support 
64bit file sizes and to the best of my knowledge this generally works. 
If it doesn't, I would suspect a specific platform problem; it would 
help to know what VM and what platform the problem occurs on.

Cheers,
   - Andreas



More information about the Squeak-dev mailing list