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
I'm not sure about how to do this with the DrRacket debugger, but you can use
`debug-repl`[1] from the `debug` package to basically set a breakpoint that
opens a REPL you can use to inspect variables in. This works in both DrRacket
and regular command line racket.
[1]
2 matches
Mail list logo
