Home | Notes | Languages | Programs | Homework |
Re: annoying error messsages |
Stephen Edwards (edwards@CS.VT.EDU)
Wed, 24 Oct 2001 10:41:54 -0400
Message-ID: <3BD6D332.C5B3F675@cs.vt.edu> Date: Wed, 24 Oct 2001 10:41:54 -0400 From: Stephen Edwards <edwards@CS.VT.EDU> Subject: Re: annoying error messsages
> Is there a way to actually find out where the error is in the code...
> instead of an annoying ";The object #t is not applicable" error message?
When you run your program interactively, it will halt on the error
condition and give you an error prompt:
2 error>
Instead of just typing (restart 1), type (debug) to enter the debugger.
Then press the h key to see the "execution history", which is basically
a stack dump.
You can find out more about debugging, tracing entry/exit of your
functions, and setting breakpoints in Section 5 of the Scheme User's
Manual.
-- Steve
-- Stephen Edwards 604 McBryde Hall Dept. of Computer Science e-mail : edwards@cs.vt.edu U.S. mail: Virginia Tech (VPI&SU) office phone: (540)-231-5723 Blacksburg, VA 24061-0106 -------------------------------------------------------------------------------
Home | Notes | Languages | Programs | Homework |