?

Log in

No account? Create an account
   Journal    Friends    Archive    Profile    Memories
 

Strange problems building sbcl on intel mac - From First Principles — LiveJournal

Aug. 15th, 2006 09:00 pm Strange problems building sbcl on intel mac

I had some strange problems building SBCL on my Intel mac mini. At least, when it was being built in a directory served by OpenAFS, the build failed eventually. After consultation with slyrus on freenode irc, I moved the sources and the 0.9.15 binary onto my local disk to do the build. And it worked fine.

So, I moved the binary that resulted out into AFS-land - and it failed to run. Hrmppphhhh. Changing the AFS owner to someone with a UID on the local box caused the sbcl binary to run. Tried the build again. Failure mode.

Just to prove I wasn't halucinating, I moved it all back to the local disk and rebuilt from scratch - which worked fine again.

The joke here is that the errors were related to malloc()ing memory from the heap - something which should have no relationship whatsoever with the fact that the image is in AFS-land.

Just for gigles, I took some C code I had lying around that did a few malloc()s and compiled and ran it. It didn't seem to make one bit of difference whether or not it was in AFS-land - nor what UID was the owner of the binary.

I'm confused, to say the least.

4 comments - Leave a commentPrevious Entry Share Next Entry

Comments:

From:(Anonymous)
Date:August 16th, 2006 07:03 am (UTC)
(Link)
whether malloc() fails is not only connected to where files being accessed reside, it is connected to almost. everything. else.

try running with: ulimit -d unlimited
From:ipmonger
Date:August 16th, 2006 07:46 am (UTC)
(Link)
ulimit reported data segment size as 6144, so I set it to unlimited. Re-ran build out of AFS-land, with the same result.
From:(Anonymous)
Date:August 16th, 2006 05:06 pm (UTC)
(Link)
ulimit -v unlimted, then?
From:ipmonger
Date:August 16th, 2006 05:29 pm (UTC)
(Link)
already unlimited:

% ulimit -a
core file size (blocks, -c) 0
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) 8164
cpu time (seconds, -t) unlimited
max user processes (-u) 100
virtual memory (kbytes, -v) unlimited