> From ····@aplcenmp.apl.jhu.edu Wed Aug 24 19:41:15 1994
> Date: Wed, 24 Aug 94 13:43:07 EDT
> From: ····@aplcenmp.apl.jhu.edu (Marty Hall)
> To: ····@lft.mw.tu-muenchen.de
> Subject: Re: interrupt bus error
> Newsgroups: comp.lang.lisp
> Organization: SAIC AI Lab, JHU P/T CS Faculty
> Cc:
> Content-Length: 427
>
> In article <···············@lft.mw.tu-muenchen.de> you write:
> >
> >i get an "interrupt bus error" message from my lisp application.
> >Knows anybody something about this error and how to avoid it?
>
> I doubt anyone can help you unless you post what you did that caused
> this error. I've seen it in places where Lisp interfaces with X; there
> are probably many, many things that can cause it.
>
> - Marty
> (proclaim '(inline skates))
>
i use your Lucid Lisp Ver. 4.1 on Sun Sparc 2 running SunOS 4.1.1
;;; Lucid Common Lisp/SPARC
;;; Development Environment Version 4.1, 12 October 1992
;;; Copyright (C) 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1992 by Lucid, Inc.
;;; All Rights Reserved
;;;
with the following features
(:GINA2 :GINA2.3 :CLM-HAS-PROCESSES :MOTIF-SERVER :CLM-NEEDS-CLX :CLOS
:MOSAIC-UNITS :SINGLE :COLOR-CW :X-SUN4-SCL4 :CLXR5 :CLX-MIT-R5 :CLX-MIT-R4
:XLIB :CLX :KEE4.1 :KEE4.0 :KEE3.1 :NOAUN :XCW :LCL4.0 :LCL4.1 :MULTITASKING
:MONITORING :PQC :COMPILER :LOOP :IEEE-FLOATING-POINT :NEWCFG :SUN-OS :SPARC
:SUN :UNIX :LCL3.0 :EGC :LUCID :COMMON-LISP)
>
and this worked very stable for a long time and a few applications.
Now i am just finishing my lisp-application - it's a large object-oriented
information system, that helps engineers in car manufactoring to design and
optimize adhesive bonded joints.
Every module is tested and debugged and now should be integrated in the whole
application.
But i receive error messages for "interrupt bus error" and "Bad pointer found
during GC" after invoking lcl::run-program to start background processes on
other hosts.
The background processes create some ascii-files for FEM-calculation and can be
called for unlimited time.
Going back to another menu-items and functions, cause a
interrupt bus error. With lcl::close-all-files the interrupt bus error can be
suppressed for a little time, but a "Bad pointer found during GC" occurs.
In my manuals, no information are available concerning this errors
or what happens exactly in lcl::make-process or related functions.
Does not really close lcl::run-program all opened streams or files?
Error message follows:
Using Application Expertensystem fuer die Klebetechnik ...
>>Trap: Interrupt: bus error
LUCID-COMMON-LISP:MAKE-PROCESS:
Keyword arg 0 (FUNCTION): #<Interpreted-Function (LAMBDA (#:G109729
#:G109730 #:G109731) (LET (# # # #) (DECLARE #)
(UNWIND-PROTECT # # #))) 4FDF51E>
Keyword arg 1 (ARGS): (#<Application Expertensystem fuer die Klebetechnik
on LOCALHOST:0> #<XLIB:DISPLAY LOCALHOST:0 (X11/NeWS -
Sun Microsystems Inc. R3000)> #S(XTK::TOOLKIT-CONNECTION STREAM 7
MOTIF-VERSION 1001 LISP-STREAM #<Stream SPLIT-STREAM 5C1D8FE> CLOSED
NIL LOCK NIL CALLBACK-TABLE #<Hash-Table 5C1DB86> EVENT-TABLE
#<Hash-Table 5C1DBD6> TIMER-TABLE #<Hash-Table 5C1DC26>
DISPATCHER-TERMINATED NIL WIDGET-ID 414 ...))
Keyword arg 2 (NAME): "Expertensystem fuer die Klebetechnik on LOCALHOST:0
Background"
Keyword arg 3 (STACK-SIZE): 20000
Keyword arg 4 (WAIT-FUNCTION): #<Compiled-Function LUCID-RUNTIME-SUPPORT:TRUE
52D35E>
Keyword arg 5 (WAIT-ARGS): NIL
Keyword arg 6 (RESTART-ACTION): :FLUSH
Keyword arg 7 (PRIORITY): 100
Keyword arg 8 (DONT-ENQUEUE): NIL
:A 0: Abort to Lisp Top Level
-> (lcl::quit)
My memory before looks like that:
(room t)
;;; 46838 words [187352 bytes] of dynamic storage in use.
;;; 1999112 words [7996448 bytes] of free storage available before a GC.
;;; 4045062 words [16180248 bytes] of free storage available if GC is disabled.
;;; Semi-space Size: 8000K bytes [125 segments]
;;; Current Dynamic Area: Dynamic-1-Area
;;; GC Status: Enabled
;;; Reserved Free Space: 41536K bytes [649 segments]
;;; Memory Growth Limit: 99904K bytes [1561 segments], total
;;; Memory Growth Rate: 3200K bytes [50 segments]
;;; Reclamation Ratio: 33% desired free after garbage collection
;;; Area Information:
;;; Name Size [used/allocated]
;;; ---- ----
;;; Ephemeral Level 0 482K/1024K bytes, 8/16 segments
;;; Ephemeral Level 1 496K/1280K bytes, 8/20 segments
;;; Ephemeral Level 2 0K/1280K bytes, 0/20 segments
;;; Ephemeral Odd-level OSP 0K/1024K bytes, 0/16 segments
;;; Ephemeral Even-level OSP 0K/1280K bytes, 0/20 segments
;;; Dynamic-0-Area 0K/8000K bytes, 0/125 segments
;;; Dynamic-1-Area 183K/7992K bytes, 3/125 segments
;;; Discardable-Static-Area 13K/64K bytes, 1/1 segment
;;; Discardable-Read-Write-Area 2832K/2880K bytes, 45/45 segments
;;; Foreign Area 1K/64K bytes, 1/1 segment
;;; Static-Area 12920K/12927K bytes, 202/202 segments
;;; Read-Write-Area 5107K/5120K bytes, 80/80 segments
;;; Readonly-Pointer-Area 2857K/2880K bytes, 45/45 segments
;;; Readonly-Non-Pointer-Area 11398K/11456K bytes, 179/179 segments
and afterwards:
-> (room t)
;;; 46838 words [187352 bytes] of dynamic storage in use.
;;; 1999112 words [7996448 bytes] of free storage available before a GC.
;;; 4045062 words [16180248 bytes] of free storage available if GC is disabled.
;;; Semi-space Size: 8000K bytes [125 segments]
;;; Current Dynamic Area: Dynamic-1-Area
;;; GC Status: Enabled
;;; Reserved Free Space: 41536K bytes [649 segments]
;;; Memory Growth Limit: 99904K bytes [1561 segments], total
;;; Memory Growth Rate: 3200K bytes [50 segments]
;;; Reclamation Ratio: 33% desired free after garbage collection
;;; Area Information:
;;; Name Size [used/allocated]
;;; ---- ----
;;; Ephemeral Level 0 121K/1024K bytes, 2/16 segments
;;; Ephemeral Level 1 569K/1280K bytes, 9/20 segments
;;; Ephemeral Level 2 0K/1280K bytes, 0/20 segments
;;; Ephemeral Odd-level OSP 0K/1024K bytes, 0/16 segments
;;; Ephemeral Even-level OSP 0K/1280K bytes, 0/20 segments
;;; Dynamic-0-Area 0K/8000K bytes, 0/125 segments
;;; Dynamic-1-Area 183K/7992K bytes, 3/125 segments
;;; Discardable-Static-Area 13K/64K bytes, 1/1 segment
;;; Discardable-Read-Write-Area 2832K/2880K bytes, 45/45 segments
;;; Foreign Area 1K/64K bytes, 1/1 segment
;;; Static-Area 12920K/12927K bytes, 202/202 segments
;;; Read-Write-Area 5107K/5120K bytes, 80/80 segments
;;; Readonly-Pointer-Area 2857K/2880K bytes, 45/45 segments
;;; Readonly-Non-Pointer-Area 11398K/11456K bytes, 179/179 segments
I tried different stack-sizes from 5000 to 20000 without any success.
In my manuals no information are available concerning this error-message.
Has anybody information about this error (>>Trap: Interrupt: bus error),
what circumstance cause this failure and are there any ways to avoid it?
Any help would be appreciated!
With friendly regards
Mit freundlichen Gruessen
Johannes Lorenz
+----------------------------------------------------------------------------+
| xxxxx x x xxxxxxx Lehrstuhl fuer Fuegetechnik |
| x x x x x x Technische Universitaet Muenchen |
| x x x x x x Arcisstrasse 21 |
| x xxxxx x x x 80333 Muenchen . . |
| Germany (_) (_) |
| | | | | |
| Phone: +49 89 21053339 | | | | |
| Fax: +49 89 21053340 | |/\| | |
| Dipl.-Ing. Johannes Lorenz |
| |
| Email (RFC-822): ········@lft.mw.tu-muenchen.de |
+----------------------------------------------------------------------------+