I posted this as a question to Stack Overflow http://stackoverflow.com/questions/27889989/stepping-in-sbcl-from-within-the-debugger (follow the link to see the description). Basically I'm trying to single step after hitting a break point with sbcl and Slime. I was able to do what I want in sbcl without using Slime by using 'start' debugger command. As far as I can tell, there is no way to use that command from the Slime debugger.
Can someone tell me if I am missing something obvious or if it is currently is not possible to step after breaking with sbcl and Slime?
On Tue, Jan 20 2015, Michael Malis wrote:
Can someone tell me if I am missing something obvious or if it is currently is not possible to step after breaking with sbcl and Slime?
There are stepping commands in the sldb buffer: s -- sldb-step o -- sldb-out x -- sldb-next
For SBCL: s calls sb-ext:step-into o calls sb-ext:step-out x calls sb-ext:step-next
And sb-impl::enable-stepping is called automatically by those commands. So it looks like the commands do something reasonable.
If I add (declare (optimize debug)) to your fib function then the commands seem work.
Helmut
I figured out the problem. I had compiled swank with debug set to 3. Because of this, when I would step after the break it would then step into swank, giving the weird behavior I described in the Stack Overflow post.
On Wed, Jan 21, 2015 at 1:44 AM, Helmut Eller eller.helmut@gmail.com wrote:
On Tue, Jan 20 2015, Michael Malis wrote:
Can someone tell me if I am missing something obvious or if it is
currently
is not possible to step after breaking with sbcl and Slime?
There are stepping commands in the sldb buffer: s -- sldb-step o -- sldb-out x -- sldb-next
For SBCL: s calls sb-ext:step-into o calls sb-ext:step-out x calls sb-ext:step-next
And sb-impl::enable-stepping is called automatically by those commands. So it looks like the commands do something reasonable.
If I add (declare (optimize debug)) to your fib function then the commands seem work.
Helmut
-
Helmut Eller -
Michael Malis