[cmucl-help] Segmentation fault when trying to use the max heap

[Raymond Toy]

>>>>> "Chisheng" == Chisheng Huang <cph at chi-square-works.com> writes:

    Chisheng> Hi,
    Chisheng> I'll get a segmentation fault when I specify -dynamic-space-size 0
    Chisheng> with the 2016-02 snapshot on a 32-bit Linux machine:

    Chisheng>   % lisp -dynamic-space-size 0
    Chisheng>   Segmentation fault
    Chisheng>   % lisp -dynamic-space-size 1700
    Chisheng>   -dynamic-space-size must be no greater than 1632 MBytes.
    Chisheng>   % lisp -dynamic-space-size 1632
    Chisheng>   Segmentation fault
    Chisheng>   % lisp -dynamic-space-size 1600
    Chisheng>   Segmentation fault
    Chisheng>   % lisp -dynamic-space-size 1550
    Chisheng>   Segmentation fault
    Chisheng>   % lisp -dynamic-space-size 1500
    Chisheng>   CMU Common Lisp snapshot-2016-02 (21A Unicode), running on whale
    Chisheng>   With core: /usr/local/cmucl-2016-02/lib/cmucl/lib/lisp-sse2.core
    Chisheng>   Dumped on: Mon, 2016-02-15 09:58:28-08:00 on lorien3
    Chisheng>   See <http://www.cmucl.org/> for support information.
    Chisheng>   Loaded subsystems:
    Chisheng>       Unicode 1.29 with Unicode version 6.2.0
    Chisheng>       Python 1.1, target Intel x86/sse2
    Chisheng>       CLOS based on Gerd's PCL 2010/03/19 15:19:03
    Chisheng>   * 

Thanks for the report.  I'm guessing that this means that address
space used for the heap overlaps some other important system space.

Can you send the output of cat /proc/<pid>/maps for the lisp process
with a heap size of 1500?  That should give a hint at what's going on.
CMUCL expects that the heap can use all of the memory from 0x58100000
to 0xbe000000.  This seems to be true on my Fedora system.

What 32-bit linux system are you running on?

--
Ray