Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!ucbvax!bloom-beacon!mit-eddie!uw-beaver!rice!sun-spots-request
From: Herbst.HENR801c@xerox.com
Newsgroups: comp.sys.sun
Subject: 3/60 Sun Common Lisp 2.1  with KEE segmentation fault
Message-ID: <2193@kalliope.rice.edu>
Date: 10 Nov 88 01:58:05 GMT
Sender: usenet@rice.edu
Reply-To: Sun-Spots@Rice.edu
Organization: Rice University, Houston, Texas
Lines: 20
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 7, Issue 21, message 1 of 12

One of my users is a knowlege engineer developing a system with KEE on Sun
Common Lisp 2.1 on a Sun 3/60 (HiRes mono, 24MB memory, 327MB disk, 60MB
swap space). 

Ocasionally (1-5+ times/week) the Lisp gives a segmentation fault and
locks or forces the Lisper to restart. Sun and Intellicorp are busy
pointing fingers at each other, any suggestions as to where to look for
the error?  We have not been able to recreate it on demand (and since I am
in another town, I haven't even seen the error).

Also - Anyone care to comment on  interfacing SCL 2.1 to C? We need both C
called by Lisp and Lisp called by C.

tom

Thomas Herbst
Net Support Engineer
Xerox Corporation
Rochester, NY 14623
Herbst.henr801c@xerox.com