-
-for OpenBSD:
- OpenBSD 3.0 has stricter ulimit values, and/or enforces them more
- strictly, than its predecessors. Therefore SBCL's initial mmap()
- won't work unless you increase the limit on the data segment from
- the OpenBSD defaults, e.g. with
- ulimit -S -d 1000000
- before you run SBCL. Otherwise SBCL fails with a message like
- "ensure_space: failed to validate xxxxxxx bytes at yyyyy". (SBCL
- is just allocating this huge address space, not actually using this
- huge memory at this point. OpenBSD <3.0 had no problem with this,
- but OpenBSD 3.0 is less hospitable.)
-
-for Darwin:
- PURIFY (which can be used alone but is also used by the system when
- saving a new core) uses more stack than the default limit on MacOS
- X.2. Therefore, in order to get PURIFY to work reliably, you need
- to increase the limit, with e.g.
- limit stack 8192 # for the default shell, tcsh
- ulimit -s 8192 # for bash
- before running SBCL. This is also necessary when building the system
- from sources, as part of the build process involves saving a new core.