From: Alan R. <al...@mu...> - 2005-04-08 16:53:27
|
Thanks for your help. It appears these settings work for me. Still curious why DYLD_LIBRARY_PATH is relevant. -Alan (def!constant read-only-space-start #x01000000) (def!constant read-only-space-end #x04ff8000) (def!constant static-space-start #x08000000) (def!constant static-space-end #x097fff00) (def!constant dynamic-space-start #x10000000) (def!constant dynamic-space-end #x3FFFF000) (def!constant dynamic-0-space-start #x10000000) (def!constant dynamic-0-space-end #x3Ffff000) (def!constant dynamic-1-space-start #x40000000) (def!constant dynamic-1-space-end #x6ffff000) #!+darwin (progn (def!constant linkage-table-space-start #x70000000) (def!constant linkage-table-space-end #x71000000) (def!constant linkage-table-entry-size 16)) -Alan On Apr 6, 2005, at 7:48 PM, Brian Mastenbrook wrote: > I've seen these malloc problems before; what's your DYLD_LIBRARY_PATH? > (or any DYLD environment variable?) > > As far as address space: I've built SBCL before with up to a 1GB heap, > though it's important to note that a 1GB heap SBCL will use up to 2GB > in the middle of GC. This isn't a problem for me (precious G5) but is > a consequence of our stop-and-copy gc. > > If you want to change this, try looking at > src/compiler/ppc/parms.lisp, at the addresses that are established for > the dynamic spaces. You should be able to find spaces that allow up to > a 1GB heap; try mallocing that amount of memory from a test program > and seeing where it puts it. > > I'm reluctant to modify SBCL to always use this much heap as it will > cut down on the ability to load foreign libraries, map files, etc. > However I might increase it some if my fights with mach-o lead me to a > general solution to reserving virtual memory addresses on OS X. > > In the future emailing sbcl-devel might be a good way to get a > response; this email address is likely going away anyway at some time > in the future, though I've been somewhat lazy about migrating > everything over. > > If you're around on IRC feel free to say hi in #lisp. If not, what are > you waiting for? > > On Apr 6, 2005, at 9:42 AM, Alan Ruttenberg wrote: > >> Hi, >> >> Saw some posts irc traffic indicating you were struggling with >> building sbcl for os x. I'm trying to do the same thing and wondering >> if you had any luck. >> I'm getting "*** malloc[2292]: Deallocation of a pointer not >> malloced: 0x7800400; This could be a double free(), or free() called >> with the middle of an allocated block; Try setting environment >> variable MallocHelp to see tools to help debug" when running >> make-target-2.sh. >> >> What I'm aiming for is building an sbcl with a larger address space - >> looks like 128M is the default. I usually use openmcl, for which this >> is not a problem, but want to run some more time consuming processes >> in a faster lisp... >> >> Any help appreciated. >> >> Thanks, >> >> Alan >> >> > -- > Brian Mastenbrook > br...@ma... > http://www.iscblog.info/ > |