[aidenn0]

I now have a good place to link to when talking about lisp debugging being the killer feature that keeps me coming back to lisp as a language.

I usually get very confused responses when I say this, as people think "single step through the code" when I say "debugger" and I respond with something like "I'm pretty sure there's a way to step through the code in SLIME, but I never learned it because I've never had a need for that."

A quick skim through the series shows that the author feels the same way; there doesn't seem to be a mention of SLDB's stepper.

[fiddlerwoaroof]

It's implementation dependent, but something like this works with sbcl:

    C-u C-c C-k ;; recompile with (debug 3)
    (step (some-function))

I also never do this

[lokedhs]

I discovered the "s" key more or less by accident. Since I learned that you actually can single-step, I've used it a few times, but most of the time it's not necessary.

Compare this to another project I've been working on which is written in Kotlin. Almost every debugging session involves a lot of single-stepping.

There is no insightful point of this reply, except for agreeing that Lisp is powerful enough that single-stepping is mostly pointless. I do add a lot of (break) statements during debugging though.