#4 Changing syscall number doesn't roll back properly

[Brian J Moore]

Say you first typed something like the attached program and then ran it. You wanted to print out the value of $a0 as an int, but forgot that print_int is syscall 1 and not syscall 4. Nevertheless, you run it and mipscope stops you at the syscall line with an invalid memory access message. At this point you realize your mistake and change the offending load immediate to load 1 into $v0.

You would expect that by changing this line, you would just be rolled back to right after the first line (li $a0, 0). However, what happens is that you stay on the syscall line and can't step back anymore. If you press play you don't get anywhere. Once you stop the program and run it again, it works fine.

[Brian J Moore]