c426c5b38d
In order for DAP to support halting the program (either manually or on a breakpoint) performing some action and then resuming execution, there needs to be a way to stop the program without clearing the internal breakpoints. This is necessary for log points and stopping the program to set breakpoints. The debugging UI makes it seem like a user should be able to set or clear a breakpoint at any time. Adding this ability to complete synchronous requests while the program is running is thus important to create a seamless user experience. This change just adds a configuration to determine whether the target should clear the stepping breakpoints, and changes the server to use this new mode. Using the new mode means that the DAP server must determine when it expect the next to be canceled and do this manually. |
||
|---|---|---|
| .. | ||
| astutil | ||
| config | ||
| dwarf | ||
| elfwriter | ||
| gobuild | ||
| goversion | ||
| locspec | ||
| logflags | ||
| proc | ||
| terminal | ||
| version | ||