David T. Lewis wrote:
Try putting a self halt in Interpreter>>primitiveAdd, which should be called when you evaluate "3+4".
Or is it bytecodePrimAdd?
David T. Lewis wrote:
The main interpreter loop is Interpreter>>interpret, which fetches bytecodes and evaluates them. You can probably put a break in InterpreterSimulator>>dispatchOn:in: which is called by #interpret and simulates the big case statement that the interpreter loop uses to dispatch bytecodes for execution.
I can easily debug the InterpreterSimulator from the beginning. But, to move from the very beginning to the point where I can debug "3+4" would be very far, long, right? Or are there any way that I can do, to just skip to the part that I'm interested with.
Thank you so much for you help.
Thanks.
Ang Beepeng