▼ |  | Errortrace: Debugging and Profiling

1 | Quick Instructions
2 | Installing Errortrace
3 | Using Errortrace
4 | Errortrace Library
5 | Re-using Errortrace Stack Tracing

Version: 4.1.4
top← prev up next →

### 1`` Quick Instructions

- Throw away ".zo" versions of your source.

- Prefix your program with

  (require errortrace)

  or start MzScheme with the -l option before the arguments to load your program:

  mzscheme -l errortrace ...

  If you want to use MzScheme interactively, include the -i flag first:

  mzscheme -i -l errortrace

- When an exception occurs, the exception handler prints something like a stack trace, most recent contexts first.

The errortrace module is strange; don’t import it into another module. Instead, the errortrace module is meant to be invoked from the top-level, so that it can install an evaluation handler, exception handler, etc.

To reuse parts of the code of errortrace, import errortrace/errortrace-lib. It contains all of the bindings described here, but does not set the compilation handler or the error display handler.

top← prev up next →