Custom Query (1030 matches)

I'm entering these SLIME / debugging problems as a Trac Ticket in light of a customer's recent e-mail about their Lisp requirements ("It would be awfully nice if the debugging information generated by the compiler allowed for easier debugging, e.g., better display of args and locals, return from frame, restart frame. Integration with Slime is a must.")

SLIME has not been updated to account for recent changes made in OpenMCL to support x86-64 processors. You may run into bugs running on those platforms.

The SLIME backtrace sometimes shows incorrect information.

return-from-frame and apply-in-frame do not work reliably. (If they work at all, it's pure luck.)

From r15343, perhaps?

ChromeKote:ccl svspire$ ./dx86cl64 -n Welcome to Clozure Common Lisp Version 1.8-r15290M (DarwinX8664)! ? (set-syntax-from-char #\u+feff #\space) T ?

ChromeKote:ccl svspire$ ./dx86cl64 -n Welcome to Clozure Common Lisp Version 1.9-dev-r15382M-trunk (DarwinX8664)! ? (set-syntax-from-char #\u+feff #\space)

Error: Array index 254 out of bounds for #<SIMPLE-VECTOR 1> . While executing: (SETF CCL::SPARSE-VECTOR-REF), in process listener(1). Type :POP to abort, :R for a list of available restarts. Type :? for other options.

1 >

On 32-bit platforms, we see:

? (open #p"/dev/null" :direction :probe :element-type '(unsigned-byte 33))
> Error: Not an ivector subtag: 170
> While executing: SUBTAG-BYTES, in process listener(1).

The 170 is subtag-simple-vector. Maybe SUBTAG-BYTES should just punt somehow if it gets a non-ivector subtag? Maybe return NIL and deal with that in OPTIMAL-BUFFER-SIZE?

(From the test suite.)