Herbst.HENR801c@xerox.com (11/10/88)
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
roberts%studguppy@lanl.gov (Doug Roberts) (12/10/88)
> 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 found many ways to get segmentation faults while running KEE on our Suns -:{.... floating point errors, operations on the wrong data types, KEE bugs, etc. etc. etc... Until we get a reasonable debugging environment for lisp on the Sun, we are all sentenced to long, painful debugging sessions when these problems occur. --Doug Douglas Roberts Los Alamos National Laboratory (505)667-4569 dzzr@lanl.gov
matheny@unisyn.com (John Matheny) (12/12/88)
In article <2193@kalliope.rice.edu> Herbst.HENR801c@xerox.com writes: >Also - Anyone care to comment on interfacing SCL 2.1 to C? We need both C >called by Lisp and Lisp called by C. IntelliCorp has a product called the "KEE/C Integration Toolkit" that facilitates this. Contact them at (415) 965-5500 for information. -- John Matheny Internet: matheny@Unisyn.COM UUCP: uunet!unisyn!matheny Unisyn, Inc., 3300 Mitchell Lane, Boulder, CO 80301 +1 303 443 7878