Re: ABCL 1.5.0 released

I have compared cl-test-grid results of 1.5.0 and 1.4.0:
https://common-lisp.net/project/cl-test-grid/abcl/abcl-diff29.html

One difference is that some systems previously failed with ERROR are now CRASHed.

This means my lisp code doesn't catch the problem, neither with handler-bind, nor with (let ((*debugger-hook* ...)) )

You can reproduce this on cl-test-grid.cloud.efficito.com
(both Mark and Erik can access through ssh [email protected]).

We will wrap (ql:quickload :antik) with this code for capturing errors:

    (block main
      (let ((*debugger-hook* (lambda (c me-or-my-encapsulation)
                              (format t "MY: DEBUGGER INVOKED ~A~%" c)
                              (return-from main "FAILED"))))
        (handler-bind ((serious-condition (lambda (c)
                                            (format t "MY: CAUGHT ~A~%" c)
                                            (return-from main "FAILED"))))
          (ql:quickload :antik))))


Full command:

 java -jar ~/lisps/abcl-bin-1.4.0/abcl.jar --noinit --nosystem --batch --eval '(require :abcl-contrib)' --eval '(load "~/cl-test-grid/work-dir/agent/quicklisp/setup.lisp")' --eval '(block main (let ((*debugger-hook* (lambda (c me-or-my-encapsulation)  (format t "MY: DEBUGGER INVOKED ~A~%" c) (return-from main "FAILED")))) (handler-bind ((serious-condition (lambda (c) (format t "MY: CAUGHT ~A~%" c) (return-from main "FAILED")))) (ql:quickload :antik))))'

This finishes as

jnaASDF could not load  because org.armedbear.lisp.Go.
MY: CAUGHT Error while trying to load definition for system gsll from pathname /home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/gsll-quicklisp-dd2e7673-git/gsll.asd: Error while trying to load definition for system cffi-libffi from pathname /home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/cffi_0.19.0/cffi-libffi.asd: org.armedbear.lisp.Go


Running the same command with ~/lisps/abcl-bin-1.5.0/abcl.jar doesn't catch the error. The console messages contain this:


[ ... many STYLE-WARNINGs ... ]

; Caught STYLE-WARNING:
;   redefining UIOP/BACKWARD-DRIVER:VERSION-COMPATIBLE-P in #P"/home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/uiop-3.2.1/backward-driver.lisp" (previously defined in NIL)

..........
#<THREAD {181C196}>: Debugger invoked on condition of type JAVA-EXCEPTION
  Java exception 'java.lang.NullPointerException'.
Restarts:
  0: ABORT Abort thread.
[1] CL-USER(1): 
#<THREAD {1C5E4BB}>: Debugger invoked on condition of type JAVA-EXCEPTION
  Java exception 'java.lang.NullPointerException'.
.

[ ... more STYLE-WARNINGs ... ]


; Compilation unit finished
;   Caught 13 WARNING conditions
;   Caught 404 STYLE-WARNING conditions

; pkg-config libffi --cflags
; ERROR: Java exception 'java.io.IOException: Cannot run program "pkg-config": java.io.IOException: error=2, No such file or directory'.


; Attempting to continue anyway.
; cc -o /home/testgrid/.cache/common-lisp/abcl-1.5.0-fasl43-linux-x86/home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/cffi_0.19.0/libffi/libffi-types__grovel-tmpUS1C6HZ0.o -c -m32 -fPIC -I/home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/cffi_0.19.0/ /home/testgrid/.cache/common-lisp/abcl-1.5.0-fasl43-linux-x86/home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/cffi_0.19.0/libffi/libffi-types__grovel.c
MY: CAUGHT Error while trying to load definition for system gsll from pathname /home/testgrid/cl-test-grid/work-dir/agent/quicklisp/dists/quicklisp/software/gsll-quicklisp-dd2e7673-git/gsll.asd: This JVM is missing the Inheritance for subprocess of standard output implementation.



I don't know whether the error capturing problem is new to ABCL 1.5.0 or it also was present in 1.4.0 but was hidden on ABCL 1.4.0 failing earlier during (ql:quckload :antik).

Best regards,
- Anton