[Openmcl-devel] how to debug this? (1 > (:B) => Don't know how to find slots of 0

Pascal J. Bourguignon pjb at informatimago.com
Fri Oct 7 11:25:36 PDT 2016

Ralf Stoye <stoye at stoye.com> writes:

> Hi,
> at first: sorry if this post is a duplicate, the first mail doesn't
> seem to reach the list.
> Using cl-markdown, i encounter a bug which even prevents a
> backtrace. sometimes i'm thrown into the kernel debugger. In any case
> the data is substantially damaged and i am not comfortable debugging
> cl-containers and other involved libraries.
> Since the code runs seamless in sbcl it may be some ccl problem (i
> understand that often some vague interpretation of the specs causes
> things like that ;-)
>> Error: Array index -20 out of bounds for #<SIMPLE-VECTOR 13> .

Most probably, you'll discover it's not a ccl problem.

Start by grepping all the sources you load for "optimize", and remove
all declaration, declaimation and proclaimation of optimize.

Then (declaim (optimize (space 0) (speed 0) (debug 3) (safety 3)))
and remove the compiled binaries, and recompile and reload the sources.

ccl will most probably tell you right away where the problem is.

__Pascal Bourguignon__                 http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk

More information about the Openmcl-devel mailing list