Steel Bank Common Lisp

Gisle S=E6lensminde <Gisle.Salensminde@...> writes:
> mmap: Cannot allocate memory
> fatal error encountered in SBCL pid 32008(tid 182901392576):
> remap_free_pages: page moved, 0x0001d2d1 =3D=3D> 0x00000000

This has been discussed on sbcl-devel a couple of times this year, you
should be able to find the discussions by searching for the error
message in the mailing list archives.

Alternatively CVS SBCL should give you an error message which explains
exactly what is wrong, and what you can do on your system to fix it.

--=20
Juho Snellman

On Wed, Jun 14, 2006 at 05:00:01PM +0200, Gisle S?lensminde wrote:
> To continue debuging I'm told (according to the error message) to use 
> SB-LDB, but according to the sbcl-internals wiki 
> (http://sbcl-internals.cliki.net/ldb), I should add :sb-ldb to the file 
> customize-target-features.lisp, but I can't find this file in the sbcl 
> source tree.

Hmm, yes. That file is not *supposed* to be in the source tree,
because the point is that it's where you make changes that shouldn't
be pulled into CVS and whatnot, but the old instructions didn't
explain that, and now that you point it out, I can see how it would be
surprising, and perhaps look more like out-of-date documentation than
like a correct explanation of what you should do to do.

I have now added some text (to http://sbcl-internals.cliki.net/ldb and
to the comments in base-target-features.lisp-expr) to try to try to
clarify that. Thanks for pointing it out.

-- 
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C  B9 25 FB EE E0 C3 E5 7C
Ubi saeva indignatio ulterius cor lacerare nequit. -- Jonathan Swift's epitaph

Juho Snellman wrote:

>Gisle Sælensminde <Gisle.Salensminde@...> writes:
>  
>
>>mmap: Cannot allocate memory
>>fatal error encountered in SBCL pid 32008(tid 182901392576):
>>remap_free_pages: page moved, 0x0001d2d1 ==> 0x00000000
>>    
>>
>
>This has been discussed on sbcl-devel a couple of times this year, you
>should be able to find the discussions by searching for the error
>message in the mailing list archives.
>
>Alternatively CVS SBCL should give you an error message which explains
>exactly what is wrong, and what you can do on your system to fix it.
>
>  
>
I did not find it on sbcl-devel (may not have searched properly), but I 
found something on the log for the #lisp IRC channel. Search for 
"mprotect" in the page at http://tunes.org/~nef/logs/lisp/06.05.30.  It 
seems like that when too much (about 1GB) of memory is allocated, the 
maximal number of mprotected regions are exeeded, and sbcl crash. The 
maximal number of mprotected regions are 65536 by default, and this can 
safely be increased, allowing more memory to be allocated, by setting a 
greater value in /proc/sys/vm/max_map_count. I do not have administrator 
access to the computer in question. That mean I have to convince the 
sysadmin to change the value. Hopefully this will solve  my problem.

Gisle S=E6lensminde <Gisle.Salensminde@...> writes:
> I did not find it on sbcl-devel (may not have searched properly), but I

I think Juho is refering besides others to a thread called "SBCL on AMD64"
starting at Mon, 13 Mar 2006 (I had similar problems).

Yours, Nicolas.