From: Peter W. <pet...@wo...> - 2002-04-23 14:18:33
|
Hi, On Tue, Apr 23, 2002 at 09:10:19AM +0100, Christophe Rhodes wrote: > Hi, > > I've been progressing in my quest to compile sbcl using clisp (2.28) as a > cross-compilation host -- it's picked up several SBCL bugs, and the > cross-compiler now runs to the extent of producing about 30 sbcl-style > fasls. However, I then get: > > *** - handle_fault error2 ! address = 0xC0 not in [0x202AB000,0x20975920) ! > SIGSEGV cannot be cured. Fault address = 0xC0. > Segmentation fault > > and I'm wondering how to track the cause of this down. It's > reproduceable, and I'm happy to try things out, but because of the > nature of my "application" I haven't exactly got a small test case :-/ > > Any ideas? > > Thanks, > > Christophe Can you compile your cross-compiler with debugging enabled? (either do this by: "./makemake --with-xyz --with-etc debug > Makefile" | alternatively, with a new cvs Clisp I think 'configure' also takes a debug option) Then try to compile SBCL - if Clisp segfaults again, you can run gdb on the core file generated, and do a backtrace. It may help. You might want to first simply try compiling with the latest Clisp cvs. Regards, Peter |