I have a lot of problems with timeouts when stepping through code This can be a pain, especially since Murphy's Law states that: The timeout shall occur at a juncture of the program's syntax that will invalidate the whole point of the debugging session ie: when you're stepping through the code and it's the change to certain variables that you want to see the timeout will occur on the event you want to see. It would be really usefull if there was a way of issuing a no-op instruction to synchronize the debugger and the back end process so I could handle such timeouts semi-gracefully instead of having to start the whole test again! Nic Ferrier
