2Installing Calltrace

NOTE: trace has no effect on code loaded as
compiled byte code (i.e., from a ".zo" file) or native code
(i.e., from a ".dll", ".so", or ".dylib"
file).

Calltrace’s instrumentation can be explicitly disabled via the
instrumenting-enabled parameter. Instrumentation is on by
default. The instrumenting-enabled parameter affects only the
way that source code is compiled, not the way that exception
information is reported.

Do not load trace before writing
".zo" files. Calltrace instruments S-expressions with
unprintable values; this works fine if the instrumented S-expression
is passed to the default eval handler, but neither the S-expression
nor its byte-code form can be marshalled to a string.