[Matlisp-users] (MAKE-COMPLEX-MATRIX ...) SIGSEGV Problem

[Michael A. K. <ma...@ll...>]

All,

  I'm using "matlisp-2.0beta-2003-10-14.tar.gz" with CMUCL 19B.  Under
FreeBSD 5.4 and 6.0 all is well.

  Under SUSE (SLES-9) and Red Hat Enterprise Linux WS, Version 3 I get
segment violation (see below).  (A long time ago I believe I saw
something like this that was attributed to shared object library
offsets changing.)  

  Has this been noted before...is there a fix?

tnx

mike


;; CMU Common Lisp 19b (19B), running on meatball.llan.ll.mit.edu
;; With core: /home/mak/bin/matlisp.core
;; Dumped on: Tue, 2006-05-09 10:13:30-04:00 on meatball.llan.ll.mit.edu
;; 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
;;     MATLISP/Pre 2.0
;; 
;; * (m:make-complex-matrix 3)
;; 
;; 
;; 
;; Error in function UNIX::SIGSEGV-HANDLER:  Segmentation Violation at #xB75F4627.
;;    [Condition of type SIMPLE-ERROR]
;; 
;; Restarts:
;;   0: [ABORT] Return to Top-Level.
;; 
;; Debug  (type H for help)
;; 
;; (UNIX::SIGSEGV-HANDLER #<unused-arg>
;;                        #<unused-arg>
;;                        #.(SYSTEM:INT-SAP #x3FFFC834))
;; Source: Error finding source: 
;; Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:  Source file no longer exists:
;;   target:code/signal.lisp.
;; 0]