Retro Error Backtrace

[Cliff]

Back in the day (Autocad 14 or so) the autolisp interpreter would spit out the variable names in the line of code that bombed instead of the values (example below), making it much easier find the problem. This may be a newbie question from an old-timer. I never took the pains to learn the VLIDE. Is there something there that solves the problem?

 

Error: bad argument type: numberp: nil
Backtrace:
[0.57] (VL-BT)
[1.53] (#<SUBR @0000018680e21a98 -lambda-> "bad argument type: numberp: nil")
[2.49] (ill-fun-hk "bad argument type: numberp: nil")
[3.44] (((MSG) (IF (NOT (MEMBER MSG (QUOTE ("console break" "Function cancelled" "quit / exit abort" "")))) (PROGN (PRINC (STRCAT "\nError: " MSG)) (IF *DEBUG* (VL-BT))))) "bad argument type: numberp: nil")
[4.39] (_call-err-hook ((MSG) (IF (NOT (MEMBER MSG (QUOTE ("console break" "Function cancelled" "quit / exit abort" "")))) (PROGN (PRINC (STRCAT "\nError: " MSG)) (IF *DEBUG* (VL-BT))))) "bad argument type: numberp: nil")
[5.33] (sys-error "bad argument type: numberp: nil")
:ERROR-BREAK.28 nil
[6.25] (- nil 8.48089)
[7.19] (C:GT)
[8.15] (#<SUBR @0000018680872c50 -rts_top->)
[9.12] (#<SUBR @00000186807c8700 veval-str-body> "(C:GT)" T #<FILE internal>)
:CALLBACK-ENTRY.6 (:CALLBACK-ENTRY)
:ARQ-SUBR-CALLBACK.3 (nil 0)
 

[GLAVCVS]

Hi
If you need to locate where the error occurred during execution, once it has happened, press CTRL-F9 and VLIDE will show you the expression where the error occurred, highlighted.
I hope this answers your question correctly