I don't have time for a long explanation, but I can say this... make sure all your new code (for your debugger) is compiled. Otherwise stepping will actually step into the new code.
Marc
On 16-Jun-08, at 11:10 PM, William Cook wrote:
More progess on Eclipse/Gambit debug:
I modified the gambit sources to create a hook allowing me to replace ##repl-within. This works pretty well (works great for hitting (step) calls in the code), but I can't get real stepping (analogous to ,s and ,l) to work. As expected, it is stepping into my debug monitor code, rather than stepping through the program being debugged. I can't tell how the stepper decides what code to step or not step.. its pretty complicated.
Any hints?
William