armedbear-ticket May 2020

armedbear-ticket@common-lisp.net

1 participants
3 discussions

[armedbear] #468: Overhaul of byte[] as java.nio.Buffer
by armedbear 26 May '20

26 May '20

#468: Overhaul of byte[] as java.nio.Buffer ----------------------------------+------------------------- Reporter: Evenson Not Org | Type: defect Status: new | Priority: critical Milestone: 1.7.0 | Component: interpreter Version: 1.7.0-dev | Keywords: Parent Tickets: | ----------------------------------+------------------------- If we represent everything as a java.nio.Buffer, we gain the ability to allocate our vectors and arrays using com.sun.jna.Memory.malloc(int) invocations. -- Ticket URL: <http://abcl.org/trac/ticket/468> armedbear <http://abcl.org> armedbear

1 1

[armedbear] #464: drakma / cl+ssl failure
by armedbear 21 May '20

21 May '20

#464: drakma / cl+ssl failure ----------------------------+--------------------------------- Reporter: charmon | Type: defect Status: new | Priority: major Milestone: | Component: compiler Version: 1.6.0-dev | Keywords: cl+ssl, ssl, drakma Parent Tickets: | ----------------------------+--------------------------------- This is probably a cl+ssl/cffi issue rather than a drakma issue, but when I try to do, e.g., {{{ (drakma:http-request "https://common-lisp.net/") }}} I get the following error: {{{ A failure in the SSL library occurred on handle #<com.sun.jna.Pointer native@0x7fa96089a760 {41501C8A}> (return code: 1). SSL error queue: error:20080078:BIO routines:bio_write_intern:uninitialized [Condition of type CL+SSL::SSL-ERROR-SSL] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {63F35033}> #<CL+SSL::SSL-ERROR-SSL {5769AA74}> #<FUNCTION {63F35033}>) 1: (APPLY #<FUNCTION {63F35033}> (#<CL+SSL::SSL-ERROR-SSL {5769AA74}> #<FUNCTION {63F35033}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<CL+SSL::SSL-ERROR- SSL {5769AA74}> #<FUNCTION {63F35033}>) 3: (INVOKE-DEBUGGER #<CL+SSL::SSL-ERROR-SSL {5769AA74}>) 4: (ERROR CL+SSL::SSL-ERROR-SSL :HANDLE #<com.sun.jna.Pointer native@0x7fa96089a760 {41501C8A}> :RET 1 ...) 5: (CL+SSL:MAKE-SSL-CLIENT-STREAM #<TWO-WAY-STREAM {50E6169D}> :VERIFY NIL :HOSTNAME "common-lisp.net" ...) 6: (#<FUNCTION {4A462CFF}>) 7: (CL+SSL::CALL-WITH-GLOBAL-CONTEXT #<com.sun.jna.Pointer native@0x7fa9609829d0 {BB3CD71}> NIL #<FUNCTION {4A462CFF}>) 8: (DRAKMA::MAKE-SSL-STREAM #<TWO-WAY-STREAM {50E6169D}> :HOSTNAME "common-lisp.net" :CERTIFICATE NIL ...) 9: (DRAKMA:HTTP-REQUEST "https://common-lisp.net/") 10: (SYSTEM::%EVAL (DRAKMA:HTTP-REQUEST "https://common-lisp.net/")) 11: (EVAL (DRAKMA:HTTP-REQUEST "https://common-lisp.net/")) }}} -- Ticket URL: <http://abcl.org/trac/ticket/464> armedbear <http://abcl.org> armedbear

1 33

[armedbear] #467: Unable to load ICS's Powerloom (2010)
by armedbear 19 May '20

19 May '20

#467: Unable to load ICS's Powerloom (2010) ----------------------------------+---------------------- Reporter: Evenson Not Org | Type: defect Status: new | Priority: major Milestone: 1.6.2 | Component: compiler Version: 1.6.0-dev | Keywords: Parent Tickets: | ----------------------------------+---------------------- Stephen Varey writes in <https://mailman.common-lisp.net/pipermail /armedbear-devel/2020-May/004059.html> {{{ I am trying to load powerloom into abcl. If you download powerloom (https://www.isi.edu/isd/LOOM/PowerLoom/download.html#PowerLoom) start abcl and then (load "~/powerloom-4.0.10/load-powerloom.lisp") ;;; assuming downloaded into home directory It fails with the following stacktrace. Can you help? }}} This has exposed a bug in the compiler. -- Ticket URL: <http://abcl.org/trac/ticket/467> armedbear <http://abcl.org> armedbear

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket May 2020