Custom Query (1030 matches)
Results (349 - 351 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #874 | fixed | Backtrace on Android + chrooted Debian | ||
| Description |
I'm trying to run CCL on an Acer Iconia A500. That's an Android tablet but I run Debian (Squeeze) in a chroot environment. CCL starts but backtraces don't seem to work: helmut@iconia:~/lisp/ccl$ uname -a Linux iconia 2.6.36.3 #3 SMP PREEMPT Fri May 13 00:20:42 CST 2011 armv7l GNU/Linux helmut@iconia:~/lisp/ccl$ rlwrap ./armcl Welcome to Clozure Common Lisp Version 1.7-dev-r14869 (LinuxARM32)! ? (/ 1 0) > Error: DIVISION-BY-ZERO detected > performing / on (1 0) > While executing: CCL::%FIXNUM-TRUNCATE, in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. 1 > b Origin 270332994 is not in the stack of NIL 1 > Is this a known problem of the ARM port? Has it something to do with the chroot tricks? Perhaps because /proc doesn't not working quite correclty with chroot? |
|||
| #873 | invalid | Segfault entering #'inspect during make-instance :around | ||
| Description |
? (defclass test () ()) ? (defmethod make-instance :around ((a standard-class) &rest args) (inspect (call-next-method))) ? (make-instance 'test) Segfault |
|||
| #872 | fixed | non-standard type of warning for shadowed clauses in typecase | ||
| Description |
The definition of TYPECASE, ETYPECASE and CTYPECASE in the standard (CLHS §5.3) allows that there be multiple clauses specifying a matching type. If a clause is completely shadowed by earlier clauses, the compiler may issue a warning. The type of the warning is explicitly mentioned to be STYLE-WARNING. The exact wording is as follows:
However, CCL issues a SIMPLE-WARNING in such situations, e. g.: (block nil
(handler-bind ((warning (lambda (w) (return (type-of w)))))
(macroexpand '(typecase nr
(long-float #\L)
(double-float #\D)
(short-float #\S)
(t #\E)))))
⇒ SIMPLE-WARNING
Which, I believe, contradicts the above disposition of the standard. One consequence is that, with ASDF, such a warning issued during the compilation of a file makes COMPILE-OP fail, signalling an error where, in fact, there should be none. |
|||
