3 ms·

I'm learning CL and whetting my appetite debugging a sizeable project with SBCL/SLIME. When I trace a certain method the system goes nuts because it reports on

I'm learning CL and whetting my appetite debugging a sizeable project with SBCL/SLIME. When I trace a certain method the system goes nuts because it reports on _all_ methods of that name and they are called a lot. What I want is to trace just the method of my request and nothing more. Instead I get flooded with useless information. Any recommendation?

chr 11y ago
For a starting point, see http://netzhansa.blogspot.no/2012/02/traces-of-awesomeness.html http://netzhansa.blogspot.no/2012/02/traces-of-awesomeness.h... , where Hans Hübner teaches how to do dynamically selective tracing with SBCL.
varjag 11y ago
With CLOS, I'd consider adding a specific :around method for tracing a particular specialized method.
- crististm 11y ago
  do you mean to add an :around method on the one I'm interested and trace that instead?
  - varjag 11y ago
    I really meant more like a wrapper printing the trace-in before (call-next-method) and trace-out after. A bit cumbersome though.
deepaksurti 11y ago
In LispWorks, tracing method is possible [1], don't know how to do that with SBCL. Trace is implementation specific, so you have to check SBCL manual to trace methods. See this gist for LW here: https://gist.github.com/dmsurti/8364dcd636829eaf83d1 https://gist.github.com/dmsurti/8364dcd636829eaf83d1 You could also tailor trace with options as listed here. [2] [1] http://www.lispworks.com/documentation/lw70/LW/html/lw-29.htm http://www.lispworks.com/documentation/lw70/LW/html/lw-29.ht... [2] http://www.lispworks.com/documentation/lw70/LW/html/lw-27.htm#pgfId-886245 http://www.lispworks.com/documentation/lw70/LW/html/lw-27.ht...