enaeher/contrail

An interactive tracing facility for Clojure

contrail's Issues

Add :within option

This would allow you to trace only those calls to a given function where another function is on the stack.

Allow redirection of trace output

Right now, you can bind *out*, but there is no way to redirect only the trace output without also redirecting other output.

Tracing across threads sucks

To wit:

contrail.core-test> (def foo identity)
#'contrail.core-test/foo
contrail.core-test> (trace #'foo)
#'contrail.core-test/foo
contrail.core-test> (pmap foo (range 5))
   0 000 ::0:: :  (#'contrail.core-test/foo 3)(#'contrail.core-test/foo 0) (#'contrail.core-test/foo 1)(#'contrail.core-test/foo 2) (#'contrail.core-test/foo 4)




 0  00:::  #'contrail.core-test/foo returned 30  0#'contrail.core-test/foo returned 1 #'contrail.core-test/foo returned 0:
:

  #'contrail.core-test/foo returned 4#'contrail.core-test/foo returned 2

(0 1 2 3 4)

Compare with clojure.tools.trace:

contrail.core> (clojure.tools.trace/trace-vars foo)
#'contrail.core/foo
contrail.core> (pmap foo (range 5))
TRACE t112227: (contrail.core/foo 1)TRACE t112228: (contrail.core/foo 3)TRACE t112230: (contrail.core/foo 2)


TRACE t112229: (contrail.core/foo 4)
TRACE t112231: (contrail.core/foo 0)
TRACE t112231: => 0TRACE t112227: => 1

TRACE t112230: => 2
TRACE t112229: => 4
TRACE t112228: => 3
(0 1 2 3 4)

Improve :report-before-fn and :report-after-fn protocols

Improve :report-before-fn and :report-after-fn protocols so that the user doesn't need to know so much about Contrail internals to handle common cases

Handle var re-definition better

When a var is redefined (e.g., by a user re-compiling a file or expression in their editor), the trace reporting wrapping of its function is blown away, and so traced-vars becomes out-of-sync with the true state of things.

I see three possible solutions:

• detect when this happens and remove the var from traced-vars
• detect when this happens and try to re-trace the var, such that trace state is preserved until the user explicitly calls untrace (this is what SBCL does, at least by default)
• stop using traced-vars and instead rely on var introspection (of all vars in all namespaces) to support the functionality of all-traced, zero-arity untrace, etc

Extra space when tracing a function with no arguments

Example:

 0: (#'contrail.core/foo )
 0: #'contrail.core/foo returned nil

Add :count option

This would let you limit trace output to the first n calls to the traced function.