Hi Jack, Thanks for your reply. Setting breakpoints is not the
problem. The problem is to set things up so that when an *error*
happens, you end up in a paused state. You don't know in advance
where/when the error is going to happen. It might not always be at
the same location or every time that location in the code is executed.
(You can do this in many other debuggers).
Btw, entering a REPL when the error happens would be fine---it doesn't
have to be inside the GUI debugger.
-CR
-CR
> --
> You received this message because you are subscribed to a topic in the Google Groups "Racket Users" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/racket-users/G7zZJ54dX1g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
racket-users...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
Dr. Charles Rich, Professor, Computer Science Department
Interactive Media and Game Development Program
Robotics Engineering Program
Worcester Polytechnic Institute, Fuller Laboratories B25b
100 Institute Road, Worcester, MA 01609-2280
Email:
ri...@wpi.edu Phone:
508-831-5945 Fax:
508-831-5776
Home:
http://www.cs.wpi.edu/~rich