Next: , Previous: , Up: Internal Routines   [Contents][Index]

15.5.641 trace

trace [, level][, /file, /loop, /block, /routine, /all, /showstats, /cputime, /showexec, /enter]

Starts tracing. When tracing, all statements are displayed just before execution, complete with line numbers in the innermost enclosing subroutine, function, block routine, or file, if the current execution level is less deep than or equal to the current threshold level. Keywords:


to trace into @files.


to trace into any kind of loop (repeat, for, etc.).


to trace into {}-delimited blocks.


to trace into user-defined subroutines, functions, and block routines.


to trace all of the above.


to also display showstats information.

The LUX code is displayed with variable names and function words (such as for and else in uppercase letters. Variables that have an undefined value get a question mark affixed. Explicit numbers are displayed with markers that indicate their data type: byte and word numbers get a b or w affixed, double numbers have a d marker either to indicate the start of the exponent, or else at their very end, long numbers have no explicit marker, and float numbers have a decimal point and/or an e to indicate the start of the exponent. If a new file is opened from which to read LUX code, then this is reported. If a user-defined subroutine or function is entered or exited, then this is reported only if tracing in that subroutine or function is enabled.

If you wish to go through the statements step by step, then use step.

See also: atomize, dump, show, echo, step, showstats

Next: , Previous: , Up: Internal Routines   [Contents][Index]