armedbear-ticket October 2012

armedbear-ticket@common-lisp.net

1 participants
50 discussions

[armedbear-ticket] [armedbear] #228: Need to implement autoloader facility for SETF functions
by armedbear 14 Feb '13

14 Feb '13

#228: Need to implement autoloader facility for SETF functions -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: 1.2.0 Component: java | Version: Keywords: | -------------------------+-------------------------------------------------- The subject says it all: we currently have infrastructure for normal functions, but we need infrastructure for SETF functions as well. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/228> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #212: ABCL crash when running test suites of many libraryies
by armedbear 13 Feb '13

13 Feb '13

#212: ABCL crash when running test suites of many libraryies ----------------------------------------------------------------------------------------------+ Reporter: https://www.google.com/accounts/o8/id?id=aitoawmcq6mzgezjmpqv2tjhvs6isymf6t… | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: other | Version: 1.0.1 Keywords: | ----------------------------------------------------------------------------------------------+ I encountered crash of ABCL 1.0.1 when running tests of many libraries. (Some work may be done to isolate the problem by experimenting with the set of libraries used, but I didn't find time for this during the last 2 month, so decided to just submit an exact way to reproduce the bug). I supposed it may be a memory issue, and increased memory by JVM options (as shown below), but it doesn't help. To ensure the problem is reproducible I've created a branch of my project and create a script which load particular version of quicklisp (quicklisp is bootstrapped in local directory to avoid interference with the quickips installation user may have on his computer). The steps to reproduce: git clone git://github.com/cl-test-grid/cl-test-grid.git cd cl-test-grid git checkout abcl-crash-reproduce java -Xmx2048M -XX:ThreadStackSize=12048 -XX:MaxPermSize=256m -jar C:\Users\anton\unpacked\abcl\abcl-bin-1.0.1\abcl.jar --noinit --nosystem --batch --load crash-abcl.lisp > crash-abcl.log 2>&1 [ ... lot of output, and after ~20 mins ABCL crashed ] crash-abcl.log is attached. The stacktrace of interest is at the bottom. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/212> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 10

[armedbear-ticket] [armedbear] #251: ffi callbacks don't unbox integer values
by armedbear 19 Dec '12

19 Dec '12

#251: ffi callbacks don't unbox integer values -----------------------+---------------------------------------------------- Reporter: sboukarev | Owner: nobody Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: java | Version: 1.1.0-dev Keywords: | -----------------------+---------------------------------------------------- It very well may be a cffi issue. Compile the following C code with gcc -shared test.c -o test.so {{{ #ifdef WIN32 #define DLLEXPORT __declspec(dllexport) #else #define DLLEXPORT #endif DLLEXPORT short test(short (*f)(short, short)) { return f(23, 24); } }}} Then {{{ (cffi:load-foreign-library "/tmp/test.so") (cffi:defcfun test :short (function :pointer)) (cffi:defcallback (test-callback) :short ((a :short) (b :short)) (+ a b)) }}} And finally {{{ (test (cffi:get-callback 'test-callback)) => The value #<java.lang.Short 23 {5EE76547}> is not of type NUMBER. }}} That's on 64-bit x86 linux, with OpenJDK 1.6.0_24 and jna downloaded by maven. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/251> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 10

[armedbear-ticket] [armedbear] #258: Compiler bug in call to MAX
by armedbear 09 Dec '12

09 Dec '12

#258: Compiler bug in call to MAX ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: compiler | Version: 1.1.0-dev Keywords: | ----------------------+----------------------------------------------------- Eric Marsten reports in http://article.gmane.org/gmane.lisp.armedbear.devel/2611: The following illustrates what looks like a bug in the compiler's handling of type propagation (bug disappears without the type declaration). {{{ CL-USER(25): (lisp-implementation-version) "1.1.0-dev-svn-14222M" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_03-b21)" "amd64-Linux-3.3.0-trunk-amd64)" CL-USER(26): (defun foo (a b) (declare (type (integer * 6488318769) b)) (max 1 (the (integer * 5711538578) a) b 2 1351352470)) FOO CL-USER(27): (foo 5711538444 6488318765) 6488318765 CL-USER(28): (compile 'foo) FOO NIL NIL CL-USER(29): (foo 5711538444 6488318765) 1351352470 }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/258> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #257: ASDF:MVN components always retrieve LATEST artifacts
by armedbear 09 Dec '12

09 Dec '12

#257: ASDF:MVN components always retrieve LATEST artifacts ------------------------------------------+--------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: other | Version: 1.1.0-dev Keywords: abcl-contrib abcl-asdf maven | ------------------------------------------+--------------------------------- ABCL-ASDF seems to be ignoring versions declared in the system definition, instead electing to load the LATEST version". {{{ (abcl-asdf:resolve (asdf:find-component (asdf:find-system :jna) "net.java.dev.jna/jna/3.4.0")) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/257> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #259: jss:jarray-to-list fails
by armedbear 09 Dec '12

09 Dec '12

#259: jss:jarray-to-list fails --------------------------------------------+------------------------------- Reporter: https://openid.fau.de/eg74yneg | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: Component: abcl-contrib | Version: Keywords: | --------------------------------------------+------------------------------- CL-USER> * #<jarray [B@5719d1 {15F987F}> CL-USER> (jss:jarray-to-list *) ========== no such method [Condition of type ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [ABORT] Return to sldb level 1. 2: [RETRY] Retry SLIME REPL evaluation request. 3: [*ABORT] Return to SLIME's top level. 4: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {149EEF3}> #<ERROR {E6942E}> #<FUNCTION {149EEF3}>) 1: (APPLY #<FUNCTION {149EEF3}> (#<ERROR {E6942E}> #<FUNCTION {149EEF3}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<ERROR {E6942E}> #<FUNCTION {149EEF3}>) 3: (INVOKE-DEBUGGER #<ERROR {E6942E}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:382) 5: org.armedbear.lisp.Java.jstatic(Java.java:462) 6: org.armedbear.lisp.Java$pf_jstatic.execute(Java.java:512) 7: org.armedbear.lisp.Primitive.execute(Primitive.java:135) 8: (JSS:JARRAY-TO-LIST #<jarray [B@5719d1 {15F987F}>) 9: (SYSTEM::%EVAL (JSS:JARRAY-TO-LIST *)) 10: (EVAL (JSS:JARRAY-TO-LIST *)) 11: (SWANK::EVAL-REGION "(jss:jarray-to-list *) ") -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/259> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #253: BABEL-TESTS fail to compile
by armedbear 09 Dec '12

09 Dec '12

#253: BABEL-TESTS fail to compile ---------------------------------------------+------------------------------ Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: interpreter | Version: 1.1.0-dev Keywords: quicklisp babel ansi-compilance | ---------------------------------------------+------------------------------ {{{ Unrecognized character name: u237 [Condition of type ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR] Restarts: 0: [RETRY] Retry compiling #<ASDF:CL-SOURCE-FILE "babel-tests" "tests" "tests">. 1: [ACCEPT] Continue, treating compiling #<ASDF:CL-SOURCE-FILE "babel- tests" "tests" "tests"> as having been successful. 2: [ABORT] Abort compilation. 3: [*ABORT] Return to SLIME's top level. 4: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {523B58F2}> #<ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR {6BE9EF9B}> #<FUNCTION {523B58F2}>) 1: (APPLY #<FUNCTION {523B58F2}> (#<ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR {6BE9EF9B}> #<FUNCTION {523B58F2}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<ALEXANDRIA.0.DEV :SIMPLE-READER-ERROR {6BE9EF9B}> #<FUNCTION {523B58F2}>) 3: (INVOKE-DEBUGGER #<ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR {6BE9EF9B}>) 4: (ERROR ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR :STREAM #<FILE-STREAM {4B71E076}> :FORMAT-CONTROL "Unrecognized character name: u~A" :FORMAT- ARGUMENTS (237)) 5: (ALEXANDRIA.0.DEV:SIMPLE-READER-ERROR #<FILE-STREAM {4B71E076}> "Unrecognized character name: u~A" 237) 6: (BABEL::SHARP-BACKSLASH-READER #<SHARP-BACKSLASH {214789AC}> #<FILE- STREAM {4B71E076}> #\\ NIL) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/253> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #190: FORMAT DOLLARSIGN fails to handle rounding negative arguments
by armedbear 09 Dec '12

09 Dec '12

#190: FORMAT DOLLARSIGN fails to handle rounding negative arguments -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: 1.0.1 Component: interpreter | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2138 Marshall Abrams reports:] {{{ It looks as if there's a bug in 1.0.0 with FORMAT's dollarsign directive's handling of negative numbers when it has to round up. (Forgive me if this is a known issue--I didn't find it when I searched the bug list and mailing list archives--or if there's something I'm misunderstanding.) The first group of examples use the F directive for comparison to show that the problem seems to be specific to dollarsign. (I added blank lines between example groups for easy reading.) The second group of examples illustrates a problem using dollarsign with negative numbers. The output is about 10x too large, and doesn't seem to be getting rounded properly. I'm guessing that the out of bounds error is the result of the same issue. The third group of examples shows that the problem doesn't seem to occur with positive numbers, although there's still an extra negative sign preprended. Thank you- Marshall Abrams Armed Bear Common Lisp 1.0.0-svn-13663 Java 1.6.0_29 Apple Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.7 seconds. Startup completed in 2.211 seconds. Type ":help" for a list of available commands. CL-USER(1): (format t "~,vf" 3 -0.1768522) -0.177 NIL CL-USER(2): (format t "~,vf" 2 -0.1768522) -0.18 NIL CL-USER(3): (format t "~,vf" 1 -0.1768522) -0.2 NIL CL-USER(4): (format t "~,vf" 0 -0.1768522) -0. NIL CL-USER(5): (format t "~$" -0.1768522) --1.6 NIL CL-USER(6): (format t "~v$" 3 -0.1768522) --1.75 NIL CL-USER(7): (format t "~v$" 2 -0.1768522) --1.6 NIL CL-USER(8): (format t "~v$" 1 -0.1768522) #<THREAD "interpreter" {10FA1B2D}>: Debugger invoked on condition of type TYPE-ERROR Array index out of bounds: 2 Restarts: 0: TOP-LEVEL Return to top level. [1] CL-USER(9): 0 CL-USER(10): (format t "~v$" 0 -0.1768522) --0. NIL CL-USER(11): (format t "~$" 0.1768522) 0.18 NIL CL-USER(12): (format t "~v$" 3 0.1768522) 0.177 NIL CL-USER(13): (format t "~v$" 2 0.1768522) 0.18 NIL CL-USER(14): (format t "~v$" 1 0.1768522) 0.2 NIL CL-USER(15): (format t "~v$" 0 0.1768522) 0. NIL }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/190> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #240: FIND-CLASS does not implement 3-argument behavior
by armedbear 09 Dec '12

09 Dec '12

#240: FIND-CLASS does not implement 3-argument behavior -----------------------+---------------------------------------------------- Reporter: rschlatte | Owner: somebody Type: defect | Status: new Priority: minor | Milestone: Component: CLOS | Version: Keywords: | -----------------------+---------------------------------------------------- Currently find-class does not use a supplied third (environment) parameter. (LispClass.java line 331 has a FIXME to that effect.) This blocks the fix for #239 since classes cannot be inspected at compile-time. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/240> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #159: COMPILE-FILE-16 and -17 failing for the wrong reason
by armedbear 09 Dec '12

09 Dec '12

#159: COMPILE-FILE-16 and -17 failing for the wrong reason ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: java | Version: Keywords: | ------------------------+--------------------------------------------------- The error emitted from COMPILE-FILE-16 and -17 is "Could not form URL for "CLTEST:COMPILE-FILE-16", with a similar message for -17. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/159> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket October 2012