全部

1·When managed code executes a breakpoint instruction or generates an exception, the runtime controller is notified.

当托管代码执行断点指令或生成异常时，将通知运行时控制器。

2·If you want to set a breakpoint at a particular line, the table gives you the memory address to store the breakpoint instruction.

如果希望在某个特定行设置一个断点，那么该表给出了用于存储断点指令的内存地址。

3·The thread that generated the breakpoint instruction or exception must not be allowed to execute during the synchronization process.

在同步进程期间，不得执行生成断点指令或异常的线程。

4·When complete, the original instruction is executed (from the breakpoint), and execution continues at that point.

执行完成之后，接着执行原始的指令(从断点开始)。

5·Execution of the probed instruction results in a breakpoint fault.

执行被探测的指令会导致断点错误。

6·When you view the breakpoint properties, this breakpoint appears as an address breakpoint with a memory location corresponding to the next executable instruction in the function.

查看断点属性时，该断点显示为一个地址断点，这个地址断点具有一个与函数中下一个可执行指令相对应的内存位置。

7·This is silly, because I should still be able to set a breakpoint based on the instruction address.

这是愚蠢的，因为我仍然可以设置的指令地址的一个断点。

8·Rather than stepping through your code line by line or instruction by instruction, you can allow your program to run until it hits a breakpoint, and then start to debug.

与逐行或逐条指令地检查代码不同的是，可以让程序一直执行，直到遇到断点，然后开始调试。

9·Rather than stepping through your code line-by-line or instruction-by-instruction, you can allow your program to run until it hits a breakpoint, then start to debug.

与逐句或逐条指令地检查代码不同的是，可以让程序一直执行，直到遇到断点，然后开始调试。