On Mon, Nov 06, 2006 at 02:39:13PM +0100, Peter Van Eynde wrote:
> Hello,
> 
> Your logs show that there is a memory layout conflict in sbcl:
> 
> On Saturday 04 November 2006 10:45, J.P. Larocque wrote:
> > > cat /proc/self/maps
> > 
> > ---8<---8<---
> > 00010000-00014000 r-xp 00000000 08:01 6201                               
> > /bin/cat
> > 00022000-00024000 rwxp 00002000 08:01 6201                               
> > /bin/cat
> > 00024000-00046000 rwxp 00024000 00:00 0                                  
> > [heap]
> > f7d24000-f7e78000 r--p 00000000 fe:00 16461                              
> > /usr/lib/locale/locale-archive
> 
> And then sbcl does an allocation of the linkage tables from 
> 0xf800000 upto 0x10000000. This goes right over where the 
> libraries are in memory:
> 
> src/compiler/sparc/parms.lisp
> ...
>   (def!constant linkage-table-space-start #x0f800000)
>   (def!constant linkage-table-space-end   #x10000000)
> 
> and in the strace:
> 
> 
> > mmap(0xf800000, 8388608, PROT_READ|PROT_WRITE|PROT_EXEC, 
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0xf800000
> 
> A while later it crashes. To fix this one would need access to 
> a sparc64 machine to further debug this problem, but vore
> is still down so I cannot use a debian machine to investigate this.

Hi Peter,

if yo want i could try to put up a sparc64 wit Debian on it
and attac it to the net.

 Cheers, RalfD

> If you can recompile sbcl you could try to change the parms.lisp file move 
> the 
> LT to some other place. Maybe #xa0000000 to #xa0800000?
> 
> Groetjes, Peter
> 
> -- 
> signature -at- pvaneynd.mailworks.org 
> http://www.livejournal.com/users/pvaneynd/
> "God, root, what is difference?" Pitr | "God is more forgiving." Dave 
> Aronson| 
> 
> 
> _______________________________________________
> cl-debian mailing list
> [EMAIL PROTECTED]
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-debian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to