[CM] Re: cannot run cm script on Linux SBCL

Bill Schottstaedt bil@ccrma.Stanford.EDU
Thu, 18 Aug 2005 04:12:38 -0700


 > If your feel adventurous you should be able to debug your problem
 > with gdb, see
 > http://sbcl-internals.cliki.net/gdb

Ok:

/home/bil/cmn/ sbcl
[... delete blathering ...]

debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" {90043E9}>:
   Invalid external-format
internal error #29
     SC: 14, Offset: 4   lispobj 0x50ba5ff
fatal error encountered in SBCL pid 3454(tid 1075396352):
internal error too early in init, can't recover
The system is too badly corrupted or confused to continue at the Lisp
level. If the system had been compiled with the SB-LDB feature, we'd drop
into the LDB low-level debugger now. But there's no LDB in this build, so
we can't really do anything but just exit, sorry.


error 29 is apparently "unseen throw tag error"


/home/bil/cmn/ gdb /home/bil/test/sbcl-0.9.3/src/runtime/sbcl
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) break call_into_c
Breakpoint 1 at 0x805aa30: file x86-assem.S, line 77.
(gdb) run --core /home/bil/test/sbcl-0.9.3/output/cold-sbcl.core
Starting program: /home/bil/test/sbcl-0.9.3/src/runtime/sbcl --core /home/bil/test/sbcl-0.9.3/output/cold-sbcl.core
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x4001c000
[...]

Program received signal SIGSEGV, Segmentation fault.
0x0a0d8d8f in ?? ()
(gdb)
(gdb) where
#0  0x0a0d8d8f in ?? ()
#1  0x00000018 in ?? ()
#2  0x0943a24f in ?? ()
#3  0x00000148 in ?? ()
#4  0x0000004f in ?? ()
#5  0x0de90a17 in ?? ()
#6  0x0a230c77 in ?? ()
#7  0x00000008 in ?? ()
#8  0x0a230c77 in ?? ()
#9  0x0a031855 in ?? ()
#10 0x405b7eb8 in ?? ()
#11 0x405b8028 in ?? ()
#12 0x00000000 in ?? ()
(gdb) x/8x 0x50ba5f0
0x50ba5f0:      0x00000000      0x00000000      0x00000000      0x00000000
0x50ba600:      0x00000000      0x00000000      0x00000000      0x00000000


A dead-end, at least for me.

I looked into including :sb-ldb from /base-target-features.lisp-expr, but
I don't have a working sbcl, so I can't (easily) rebuild it.  And I can't see what
good it would do -- I know nothing about cmu's ldb or sbcl internals.