3 ms·
CIDER has had debugging abilities like this for a year, there's a sexp based interactive debugger that allows injection, evaluation, stepping etc. Here's a 39
by ane 10y ago
CIDER has had debugging abilities like this for a year, there's a sexp based interactive debugger that allows injection, evaluation, stepping etc.
Here's a 39 second video about it https://www.youtube.com/watch?v=A3JAlWM8qRM https://www.youtube.com/watch?v=A3JAlWM8qRM
- lispm 10y agoThe debugger needs to 'instrument' the code with breakpoints...? That's something different. In a Lisp system I would have an arbitrary amount of code and can halt and inspect/debug any code without any prior need to 'instrument' code.
- ane 10y agoTo debug a function, yes, you need to eval the form using instrumentation. Then the debugger starts when this form is evaluated. This is the the only major difference to what SLIME provides. Adding breakpoints is somewhat easier with cider, you don't need to call break but you can just add a breakpoint to any sexp by pressing b.
- lispm 10y ago> Then the debugger starts when this form is evaluated. You mean the stepper using break-instrumented code? That's just a part of what one would call 'debugger' in Lisp. What CIDER calls 'debugger' would be mostly called 'stepper' in Lisp. http://franz.com/products/allegro-common-lisp/stepper_dialog.lhtml http://franz.com/products/allegro-common-lisp/stepper_dialog... http://www.lispworks.com/documentation/lw70/IDE-M/html/ide-m-186.htm#pgfId-853131 http://www.lispworks.com/documentation/lw70/IDE-M/html/ide-m... > Adding breakpoints is somewhat easier with cider, you don't need to call break but you can just add a breakpoint to any sexp by pressing b. LispWorks does that, too. Usually via a break icon in the window toolbar or the context menu.