loading libraries in abcl causes java stack-overflow
Mirko Vukovic
mirko.vukovic at gmail.com
Mon Jan 9 15:39:03 UTC 2017
Hello,
This is on Windows 10 and ABCL 1.4.0. I use the library Vecto as an
example.
When I start ABCL in a command window, I can load Vecto using asdf or ql.
If I do the same from Slime (2.18), I get a java stack overflow:
Stack overflow.
[Condition of type STORAGE-CONDITION]
Restarts:
0: [*ABORT] Return to SLIME's top level.
1: [ABORT] Abort thread.
Backtrace:
0: (#<FUNCTION {3C85E}> #<STORAGE-CONDITION {1B526DF}> #<FUNCTION
{3C85E}>)
1: (APPLY #<FUNCTION {3C85E}> (#<STORAGE-CONDITION {1B526DF}> #<FUNCTION
{3C85E}>))
2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<STORAGE-CONDITION
{1B526DF}> #<FUNCTION {3C85E}>)
3: (INVOKE-DEBUGGER #<STORAGE-CONDITION {1B526DF}>)
4: org.armedbear.lisp.Lisp.stackError(Lisp.java:388)
5: org.armedbear.lisp.swank_513.execute(swank.lisp:1677)
6: org.armedbear.lisp.LispThread.execute(LispThread.java:851)
7: org.armedbear.lisp.Primitives$pf_apply.execute(Primitives.java:2800)
8: (SWANK:EVAL-FOR-EMACS (SWANK-REPL:LISTENER-EVAL "(asdf:load-system
:vecto)
") "COMMON-LISP-USER" 35)
9: (APPLY #<EVAL-FOR-EMACS {1EBB63}> ((SWANK-REPL:LISTENER-EVAL
"(asdf:load-system :vecto)
") "COMMON-LISP-USER" 35))
10: (SWANK::PROCESS-REQUESTS NIL)
11: (#<FUNCTION {B14FE}>)
12: (#<FUNCTION {1BEFA9A}>)
13: (FUNCALL #<FUNCTION {1BEFA9A}>)
14: ((FLET SWANK/BACKEND:CALL-WITH-DEBUGGER-HOOK) #<SWANK-DEBUGGER-HOOK
{1BBCB67}> #<FUNCTION {1BEFA9A}>)
15: (APPLY #<(FLET CALL-WITH-DEBUGGER-HOOK) {136C698}>
#<SWANK-DEBUGGER-HOOK {1BBCB67}> #<FUNCTION {1BEFA9A}> NIL)
16: (SWANK/BACKEND:CALL-WITH-DEBUGGER-HOOK #<SWANK-DEBUGGER-HOOK
{1BBCB67}> #<FUNCTION {1BEFA9A}>)
17: (#<FUNCTION {128469A}>)
18: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-INPUT* .
#S(SLIME-INPUT-STREAM)) (*STANDARD-OUTPUT* . #S(SLIME-OUTPUT-STREAM))
(*TRACE-OUTPUT* . #S(SLIME-OUTPUT-STREAM)) (*ERROR-OUTPUT* .
#S(SLIME-OUTPUT-STREA..
19: (SWANK::HANDLE-REQUESTS #S(SWANK::MULTITHREADED-CONNECTION :SOCKET
#<java.net.ServerSocket ServerSocket[addr=0.0.0.0/0.0.0..... {694679}>
:SOCKET-IO #<TWO-WAY-STREAM {191E155}> :DEDICATED-OUTPUT NIL :..
20: (SWANK-REPL::REPL-LOOP #S(SWANK::MULTITHREADED-CONNECTION :SOCKET
#<java.net.ServerSocket ServerSocket[addr=0.0.0.0/0.0.0..... {694679}>
:SOCKET-IO #<TWO-WAY-STREAM {191E155}> :DEDICATED-OUTPUT NIL :U..
21: (#<FUNCTION {138F959}>)
22: (SWANK::CALL-WITH-BINDINGS NIL #<FUNCTION {138F959}>)
23: (#<FUNCTION {17A5212}>)
24: (FUNCALL #<FUNCTION {17A5212}>)
25: (#<FUNCTION (LAMBDA ()) {1A24795}>)
26: (THREADS::THREAD-FUNCTION-WRAPPER #<FUNCTION (LAMBDA ()) {1A24795}>)
I have several other issues with ABCL (running from command-line) such as
uiop's run-program, loading cffi.
I have reported them on the asdf and abcl lists. I am not sure if there is
a common thread in all.
Mirko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/slime-devel/attachments/20170109/a10be4ff/attachment.html>
More information about the slime-devel
mailing list