[Openmcl-devel] How to debug?

[Hans Hübner]

Ralph,

I use TRACE [1], break, stack traces in Slime and good old print
statement debugging, like back in the day.  One of the most useful
facilities in Slime's debugger is, by the way, that you can place your
cursor on any stack frame and press "v" to go to the source location
of the invocation.  Also, a stack frame can be expanded by Enter.  In
my experience, CCL's source location is pretty good, and I tend to not
miss single stepping too much.  Sometimes, it helps to recompile a
file with full debugging (C-u C-c C-k) to get better debug info,
although CCL is pretty good by default.

-Hans

[1] http://netzhansa.blogspot.de/2012/02/traces-of-awesomeness.html

On Fri, Nov 16, 2012 at 10:25 AM, Ralph Möritz
<ralph.moeritz at outlook.com> wrote:
> 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
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel