This exception is usually a trap (a kind of exception, which in itself is a kind of interrupt) that is raised by the processor.
General debug script:
- Breakpoint pressed
- The user asks the debugger "one step" for exactly one line of code
- a line of code is executed
- CPU boosts one-step execution (exception code 1)
- The debugger catches a one-step exception (and usually handles it nicely by highlighting the next line and updating the clock)
However, this exception can also be raised in other cases. You can refer to http://support.microsoft.com/kb/117389 as a starting point.
Ramsey
source share