[Openmcl-devel] How to debug?

[Ralph Möritz]

Okay, so I just found this[1] message from the archives that seems to
indicate that STEP is considered obsolete. I also confirmed that CCL's
step does nothing (via macroexpand-1). So my question can then be
rephrased as: What debugging facilities exist in CCL that are
considered useful?

Ralph.

[1] http://www.clozure.com/pipermail/openmcl-devel/2010-January/010873.html


----------------------------------------
> From: ralph.moeritz at outlook.com
> To: openmcl-devel at clozure.com
> Date: Fri, 16 Nov 2012 10:03:45 +0200
> Subject: [Openmcl-devel] How to debug?
>
> Hello,
>
> I'm trying to debug a fairly complex library and would just like to
> ask for some advice on how to go about doing so. I'm used to debugging
> C++ and Go code using gdb and C# using Visual Studio, so the Common
> Lisp approach to debugging via SLIME is somewhat foreign to me. I've
> read up on BREAK and TRACE but what I really want is a way to step
> into the code in order to better understand its workings. I've read
> the CLHS page on STEP which is very vague and mentions that the
> behaviour is implementation-defined. I've tried calling STEP on some
> simple functions but it seems as though the functions are just run
> normally - am I missing some detail here?
>
> TIA,
> Ralph
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel