All Posts Discuss About Contact

Pelure

Ephemeral musings, often about Clojure

Swank Clojure gets a Break with the Local Environment

Recently I got fed up with a couple of warts in swank-clojure, so I made a couple of small fixes, and that lead to a couple of new features. Using SLIME with Clojure has never been as smooth as using it with Common Lisp, and the lack of debug functionality beyond the display of stack traces is particularly onerous. Recently, George Jahad and Alex Osborne's debug-repl showed the possibility of adding a break macro to enter the debugger with the call stack intact and local variables visible. This functionality is now in swank-clojure.

Consider the following example, adapted from debug-repl:

   (let [c 1
        d 2]     (defn a [b c]       (swank.core/break)       d))   (a "foo" "bar")

Running this now brings up the following SLDB debug frame:

 BREAK:   [Thrown class java.lang.Exception]
Restarts:  0: [QUIT] Quit to the SLIME top level  1: [CONTINUE] Continue from breakpoint
Backtrace:   0: user$eval1666$a1667.invoke(NOSOURCEFILE:1)   1: user$eval__1670.invoke(NOSOURCEFILE:1)   2: clojure.lang.Compiler.eval(Compiler.java:5358)   3: clojure.lang.Compiler.eval(Compiler.java:5326)   4: clojure.core$eval__4157.invoke(core.clj:2139)   –more–

As you can see, the stack trace reflects the location of the breakpoint, and there is a CONTINUE restart. Pressing "1", or Enter on the CONTINUE line, or clicking the CONTINUE line should all cause the the debugger frame to close, and the result of the function call, 2, to be displayed in the REPL frame.

Enter, or "t", on the first line of the stacktrace causes the local variables to be displayed:

 BREAK:   [Thrown class java.lang.Exception]
Restarts:  0: [QUIT] Quit to the SLIME top level  1: [CONTINUE] Continue from breakpoint
Backtrace:   0: user$eval1666$a1667.invoke(NOSOURCEFILE:1)       Locals:         b = foo         d = 2         c = bar   1: user$eval__1670.invoke(NOSOURCEFILE:1)   2: clojure.lang.Compiler.eval(Compiler.java:5358)   3: clojure.lang.Compiler.eval(Compiler.java:5326)   4: clojure.core$eval__4157.invoke(core.clj:2139)   –more–

Pressing enter on one of the local variable lines will pull up the SLIME inspector with that value. If you go back to the REPL without closing the SLDB frame, there will be no prompt, but pressing enter should give you one. The local variables are then all be avaiable for evaluation form the REPL.

Should an error occur while you are using the REPL, you will be placed in a nested debug session, with an "ABORT" restart to return to the previous debug level.

Finally, restarts are now displayed for each of the exceptions in the exception cause chain.

   (let [c 1
        d 2]     (defn a [b c]       (throw (Exception. "top" (Exception. "nested" (Exception. "bottom"))))       d))   (a "foo" "bar")

This will bring up the debugger with 2 cause restarts, which can be used to examine the related stack traces.

 top    [Thrown class java.lang.Exception]
Restarts:   0: [QUIT] Quit to the SLIME top level   1: [CAUSE1] Invoke debugger on cause  nested [Thrown class java.lang.Exception]   2: [CAUSE2] Invoke debugger on cause   bottom [Thrown class java.lang.Exception]
Backtrace:    0: user$eval1752$a1753.invoke(NOSOURCEFILE:1)    1: user$eval__1756.invoke(NOSOURCEFILE:1)    2: clojure.lang.Compiler.eval(Compiler.java:5358)    3: clojure.lang.Compiler.eval(Compiler.java:5326)    4: clojure.core$eval__4157.invoke(core.clj:2139)   –more–

The break functionality is known only to work from the REPL thread at the moment. With that small proviso, I hope you enjoy the new functionality - at least it provides a basic debug functionality until full JPDA/JDI integration is tackled.

Discuss this post here.

Published: 2010-03-31

Archive