18.5 Debugging
Racket’s built-in debugging support is limited to context (i.e., “stack trace”) information that is printed with an exception. In some cases, disabling the JIT compiler can affect context information. The errortrace library supports more consistent (independent of the JIT compiler) and precise context information. The racket/trace library provides simple tracing support. Finally, the DrRacket programming environment provides much more debugging support.
18.5.1 Tracing
(require racket/trace) | package: base |
The racket/trace library mimics the tracing facility available in Chez Scheme.
syntax
(trace id ...)
When traced procedures invoke each other, nested invocations are shown by printing a nesting prefix. If the nesting depth grows to ten and beyond, a number is printed to show the actual nesting depth.
The trace form can be used on an identifier that is already traced. In this case, assuming that the variable’s value has not been changed, trace has no effect. If the variable has been changed to a different procedure, then a new trace is installed.
Tracing respects tail calls to preserve loops, but its effect may be visible through continuation marks. When a call to a traced procedure occurs in tail position with respect to a previous traced call, then the tailness of the call is preserved (and the result of the call is not printed for the tail call, because the same result will be printed for an enclosing call). Otherwise, however, the body of a traced procedure is not evaluated in tail position with respect to a call to the procedure.
The result of a trace expression is #<void>.
Examples: | |||||||||||||||||||||||||||||||
|
syntax
(trace-define id expr)
(trace-define (head args) body ...+)
Examples: | ||||||||||||||||||
|
Examples: | ||||||||
|
syntax
(trace-define-syntax id expr)
(trace-define-syntax (head args) body ...+)
For example:
Examples: | |||||||||||
|
By default, trace prints out syntax objects when tracing a macro. This can result in too much output if you do not need to see, e.g., source information. To get more readable output, try this:
Examples: | ||||||||||||||||||||||||||
|
syntax
(trace-lambda [#:name id] args expr)
Example: | |||||
|
syntax
(trace-let id ([arg expr] ...+) body ...+)
Example: | |||||||||||||||||||
|
syntax
(untrace id ...)
The result of an untrace expression is #<void>.
parameter
(current-trace-notify) → (string? . -> . any)
(current-trace-notify proc) → void? proc : (string? . -> . any)
procedure
(trace-call id proc #:<kw> kw-arg ...) → any/c
id : symbol? proc : procedure? kw-arg : any/c
parameter
(current-trace-print-args) →
(-> symbol? list? (listof keyword?) list? number? void?) (current-trace-print-args trace-print-args) → void?
trace-print-args :
(-> symbol? list? (listof keyword?) list? number? void?)
parameter
(current-trace-print-results) →
(-> symbol? list? number? any) (current-trace-print-results trace-print-results) → void?
trace-print-results :
(-> symbol? list? number? any)
parameter
(current-prefix-in prefix) → void? prefix : string?
It defaults to ">".
parameter
(current-prefix-out prefix) → void? prefix : string?
It defaults to "<".