[CM] Newbie learning. . . . CM / CLM-3 / SND / Scheme???

[Bill Schottstaedt]

> It's not that bad, surely?

Try cmucl under gdb:

/home/bil/clm/ gdb /home/bil/test/cmucl/bin/lisp
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(gdb) run
Starting program: /home/bil/test/cmucl/bin/lisp 
CMU Common Lisp 19d (19D), running on fatty3
With core: /home/bil/test/cmucl/lib/cmucl/lib/lisp.core
Dumped on: Wed, 2006-11-15 18:43:04-08:00 on lorien
See <http://www.cons.org/cmucl/> for support information.
Loaded subsystems:
    Python 1.1, target Intel x86
    CLOS based on Gerd's PCL 2004/04/14 03:32:47
* (load "all.lisp")

; Loading #P"/home/bil/clm/all.lisp".
;   using existing configuration file mus-config.h
;; Loading #P"/home/bil/clm/clm-package.x86f".
;; Loading #P"/home/bil/clm/initmus.x86f".
;;; Opening as shared library /home/bil/clm/libclm.so ...
;;; Done.
;; Loading #P"/home/bil/clm/sndlib2clm.x86f".
;; Loading #P"/home/bil/clm/defaults.x86f".
;; Loading #P"/home/bil/clm/ffi.x86f".
;; Loading #P"/home/bil/clm/mus.x86f".
;; Loading #P"/home/bil/clm/run.x86f".

Program received signal SIGSEGV, Segmentation fault.
0x11239e8d in ?? ()
(gdb) where
#0  0x11239e8d in ?? ()
#1  0x581025e3 in ?? ()
#2  0x581026db in ?? ()
etc.

In previous times, it would run, but the stack trace was garbage.
Not to belabor this, but you should try Clisp's backtrace sometime;
if suffering is the path to wisdom...