armedbear-ticket December 2020

armedbear-ticket@common-lisp.net

1 participants
2 discussions

[armedbear] #483: Failed JVM:OFFSET assertion compiling Maxima <file:///maxima-code/share/odepack/load-dlsode.lisp>
by armedbear 23 Dec '20

23 Dec '20

#483: Failed JVM:OFFSET assertion compiling Maxima <file:///maxima- code/share/odepack/load-dlsode.lisp> -------------------------------+---------------------- Reporter: Mark Evenson | Type: defect Status: new | Priority: major Milestone: 1.8.1 | Component: compiler Version: 1.8.1-dev | Keywords: Parent Tickets: | -------------------------------+---------------------- In <https://mailman.common-lisp.net/pipermail/armedbear- devel/2020-December/004192.html> Robert Dodier writes: {{{ I know it may be hard to see what's going on but, I'm trying to load a lisp file into Maxima compiled with ABCL, and I get the error shown below: The assertion (<= -32768 JVM::OFFSET 32767) failed. I've also included a stack trace if that helps. I can supply more info if you tell me what to look for. Thanks so much for your help, Robert Dodier PS. This is in a Maxima session after compiling and launching Maxima. (%i1) :lisp (load "../share/odepack/load-dlsode.lisp") ; (IN-PACKAGE "ODEPACK") ; (LET (# # ...) ...) Error loading /Users/dodier/tmp/maxima-code/share/odepack/load-dlsode.lisp at line 25 (offset 770) #<THREAD "interpreter" {19E01A93}>: Debugger invoked on condition of type SIMPLE-ERROR The assertion (<= -32768 JVM::OFFSET 32767) failed. Restarts: 0: CONTINUE Retry assertion. 1: MACSYMA-QUIT Maxima top-level 2: TOP-LEVEL Return to top level. [1] ODEPACK(5): :bt 0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<SIMPLE-ERROR {6789AA04}>) 2: (ERROR #<SIMPLE-ERROR {6789AA04}>) 3: (SYSTEM::ASSERT-ERROR (<= -32768 JVM::OFFSET 32767) NIL NIL) 4: (JVM::CODE-BYTES #<(VECTOR T 18397) {4783535E}>) 5: (JVM::FINALIZE-CODE-ATTRIBUTE #<JVM::CODE-ATTRIBUTE {43CBA720}> NIL #<JVM::ABCL-CLASS-FILE {67BB799A}>) 6: (JVM::FINALIZE-ATTRIBUTES (#<JVM::CODE-ATTRIBUTE {43CBA720}>) NIL #<JVM::ABCL-CLASS-FILE {67BB799A}>) 7: (JVM::FINALIZE-METHOD #<JVM::JVM-METHOD {72946D27}> #<JVM::ABCL-CLASS-FILE {67BB799A}>) }}} -- Ticket URL: <https://abcl.org/trac/ticket/483> armedbear <https://abcl.org> armedbear

1 0

[armedbear] #479: CLOS MOP bug in 1.8.0
by armedbear 19 Dec '20

19 Dec '20

#479: CLOS MOP bug in 1.8.0 -------------------------------+-------------------- Reporter: Mark Evenson | Type: defect Status: new | Priority: major Milestone: 1.8.1 | Component: (A)MOP Version: 1.8.1-dev | Keywords: Parent Tickets: | -------------------------------+-------------------- Pascal Costanza reports in <https://mailman.common-lisp.net/pipermail /armedbear-devel/2020-November/004189.html>: {{{ I have encountered a bug in 1.8.0 when doing my regular Closer to MOP checks. This must be a new bug, because 1.7.1 was fine. Here is the case that triggers the problem: (use-package :mop) (defclass test-direct-slot-definition (standard-direct-slot-definition) ()) (defclass test-effective-slot-definition (standard-effective-slot-definition) ()) (defclass test-class (standard-class) ()) (defmethod validate-superclass ((class test-class) (superclass standard-class)) t) (defmethod direct-slot-definition-class ((class test-class) &rest initargs) (declare (ignore initargs)) (find-class 'test-direct-slot-definition)) (defmethod effective-slot-definition-class ((class test-class) &rest initargs) (declare (ignore initargs)) (find-class 'test-effective-slot-definition)) (defclass test-object () ((some-slot :accessor some-slot :initarg :some-slot :initform 'some-slot :type symbol :allocation :class :documentation "a slot")) (:metaclass test-class)) (unless (class-finalized-p (find-class 'test-object)) (finalize-inheritance (find-class 'test-object))) Armed Bear Common Lisp 1.8.0 Java 15.0.1 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.134 seconds. Startup completed in 0.65 seconds. Loading /Users/costanza/.abclrc completed in 6.061 seconds. Type ":help" for a list of available commands. CL-USER(1): (load "test.lisp") Error loading /Users/costanza/Temp/test.lisp at line 36 (offset 943) #<THREAD "interpreter" {1970D65C}>: Debugger invoked on condition of type UNBOUND-SLOT The slot LOCATION is unbound in the object #<TEST-EFFECTIVE-SLOT- DEFINITION {556F331F}>. Restarts: 0: TOP-LEVEL Return to top level. [1] CL-USER(2): :bt 0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<UNBOUND-SLOT {67D22A29}>) 2: (ERROR UNBOUND-SLOT :INSTANCE #<TEST-EFFECTIVE-SLOT-DEFINITION {556F331F}> :NAME SYSTEM::LOCATION) 3: (#<FUNCTION #<FUNCTION {22446549}> {22446549}> (#<STANDARD-CLASS TEST-EFFECTIVE-SLOT-DEFINITION {6670307A}> #<TEST-EFFECTIVE-SLOT-DEFINITION {556F331F}> SYSTEM::LOCATION)) 4: (SLOT-VALUE #<TEST-EFFECTIVE-SLOT-DEFINITION {556F331F}> SYSTEM::LOCATION) 5: (SLOT-DEFINITION-LOCATION #<TEST-EFFECTIVE-SLOT-DEFINITION {556F331F}>) 6: (MOP::STD-FINALIZE-INHERITANCE #<TEST-CLASS TEST-OBJECT {67510DAF}>) 7: (#<FUNCTION #<FUNCTION {2C5408FE}> {2C5408FE}> (#<TEST-CLASS TEST-OBJECT {67510DAF}>)) I believe the bug is triggered by find-class or class-finalized-p, but not sure. }}} -- Ticket URL: <https://abcl.org/trac/ticket/479> armedbear <https://abcl.org> armedbear

1 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket December 2020