title: Examine values of local variables in SLIME debugger?
body: <p>I'm in search for a better technique for doing it. My general struggle is with the fact that debugger enters either too late or too early to be able to catch the value of the variables.</p>
  
  <p>What I tried first:</p>
  
  <pre><code>(loop for i from 0 to 10 do
    (break))
  </code></pre>
  
  <p>When debugger enter on break, I can't access <code>i</code> :( So it's a wasted effort. I've tried <code>e</code> option of debugger (eval in frame), but SLIME generally just bugs out, and I have to reconnect to SWANK. <code>v</code> or <code>t</code> don't help, because the variable just "isn't there".</p>
  
  <p>What I ended up doing:</p>
  
  <pre><code>(loop for i from 0 to 10 do
    (signal i))
  </code></pre>
  
  <p>This is stupid, but works, because it puts <code>i</code> on the stack of the frame I can examine in debugger. But this is just... well, it's hackish in the worst sense of the word. Isn't there some way to "watch" a variable, or have a more meaningful way to put a breakpoint, such that I can see more variables around the place the breakpoint is entered?</p>