AutoLISP Reference Guide > AutoLISP Functions > T Functions > 
trace
 
 
 

Aids in AutoLISP debugging

(trace [function...])

The trace function sets the trace flag for the specified functions. Each time a specified function is evaluated, a trace display appears showing the entry of the function (indented to the level of calling depth) and prints the result of the function.

If Visual LISP is active, trace output is sent to the Visual LISP Trace window. If Visual LISP is not active, trace output goes to the AutoCAD command window.

NoteOnce you start Visual LISP during an AutoCAD session, it remains active until you exit AutoCAD. Therefore, all trace output prints in the Visual LISP Trace window for the remainder of that AutoCAD session. Exiting or closing Visual LISP while AutoCAD is running only closes the IDE windows and places Visual LISP in a quiescent state; it does not result in a true shutdown. You must reopen Visual LISP to view the output in the Trace window.

Use untrace to turn off the trace flag.

Arguments

function

A symbol that names a function. If no argument is supplied, trace has no effect.

Return Values

The last function name passed to trace. If no argument is supplied, trace returns nil.

Examples

Define a function named foo and set the trace flag for the function:

Command: (defun foo (x) (if (> x 0) (foo (1- x))))

FOO

Command: (trace foo)

FOO

Invoke foo and observe the results:

Command: (foo 3)

Entering (FOO 3)

 Entering (FOO 2)

  Entering (FOO 1)

   Entering (FOO 0)

   Result: nil

  Result: nil

 Result: nil

Result: nil

Clear the trace flag by invoking untrace:

Command: (untrace foo)

FOO

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@entercad.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.