bug#8884: closed (Re: bug#8884: wide-int crash)

[Peter Dyballa]

Am 19.10.2011 um 03:47 schrieb Paul Eggert:

> I'm not familiar with this error format, but I expect it's some
> Mac OS X thing.

Likely. Google seems to indicate this.

> Or perhaps your applications have a system-imposed limit
> (try the shell command "ulimit -a").

Not likely:

        core file size          (blocks, -c) unlimited
        data seg size           (kbytes, -d) unlimited
        file size               (blocks, -f) unlimited
        max locked memory       (kbytes, -l) unlimited
        max memory size         (kbytes, -m) unlimited
        open files                      (-n) 256
        pipe size            (512 bytes, -p) 1
        stack size              (kbytes, -s) 8192
        cpu time               (seconds, -t) unlimited
        max user processes              (-u) 266
        virtual memory          (kbytes, -v) unlimited


> A single 32-bit process can't possibly allocate more than 4 GiB of
> address space, so as long as there's plenty of swap space (which
> there appears to be), it's an address-space limit you're running
> into, not a swap-space limit.


It seems the limit starts to be turned on around 3 GiB... From here it  
succeeds or does not succeed to load a file greater than 10 MiB. It  
even plays a role whether I load the 1 GiB or the 2 GiB file first...

--
Greetings

  Pete

A common mistake that people make when trying to design something  
completely foolproof is to underestimate the ingenuity of complete  
fools.
        - Douglas Adams, »Mostly Harmless«