Next: Preparing code for mdprof profiling, Previous: Controlling trace goals, Up: Invocation [Contents][Index]
--trace {minimum, shallow, deep, rep, default}
Generate code that includes the specified level of execution tracing. See Debugging.
--exec-trace-tail-rec
Generate TAIL events for self-tail-recursive calls instead of EXIT events. This allows these recursive calls to reuse their parent call’s stack frame, but it also means that the debugger won’t have access to the contents of the reused stack frames.
--trace-optimized
--trace-optimised
Do not disable optimizations that can change the trace.
--event-set-file-name filename
Get the specification of user-defined events from filename.
--no-delay-death
When the trace level is ‘deep’, the compiler normally preserves the values of variables as long as possible, even beyond the point of their last use, in order to make them accessible from as many debugger events as possible. However, it will not do so if the user specifies ‘--no-delay-death’. This may be necessary if without it, the stack frames of some procedures grow too big.
--delay-death-max-vars N
Delay the deaths of variables only when the number of variables in the procedure is no more than ‘N’. The default value is 1000.
--stack-trace-higher-order
Enable stack traces through predicates and functions with higher-order arguments, even if stack tracing is not supported in general.