[plt-scheme] Can't compile 372 on PPC64

From: Matthew Flatt (mflatt at cs.utah.edu)
Date: Fri Mar 14 19:10:12 EDT 2008

At Fri, 14 Mar 2008 21:26:52 +0000, "Paulo J. Matos" wrote:
> (gdb) handle SIGSEGV nostop noprint
> Signal        Stop      Print   Pass to program Description
> SIGSEGV       No        No      Yes             Segmentation fault
> (gdb) c
> Continuing.
> Seg fault (internal error) at 0x40000031000
> Program received signal SIGABRT, Aborted.
> 0x0000040000182d64 in .raise () from /lib/libc.so.6
> (gdb) bt
> #0  0x0000040000182d64 in .raise () from /lib/libc.so.6
> #1  0x0000040000184954 in .abort () from /lib/libc.so.6
> #2  0x000000001016fcb0 in fault_handler (sn=<value optimized out>,
> si=<value optimized out>,
>     ctx=<value optimized out>) at ./sighand.c:20
> #3  <signal handler called>
> #4  symbol_bucket (table=0x400002c6c58, key=0x40000000008 "", length=33685760,
>     naya=0x40000000000) at xsrc/symbol.c:39
> #5  0x0000000010131c2c in symbol_bucket (table=<value optimized out>,
>     key=<value optimized out>, length=14, naya=0x400002d0fbc) at
> xsrc/symbol.c:111

So, it crashed right away.

Actually, looking again at the initial SIGSEGV, it's probably not a
valid place for a write barrier after all. (I misread the stack trace,
which on first glance looked like the usual place in a hashing function
where the first write barrier is often hit.)

> Do you think it's worth a try the current SVN head?

Yes, that's a good idea. Now that you suggest it, I remember that
Andrew Reilly tracked down and fixed a 64-bit GC bug a few weeks ago.


Posted on the users mailing list.