Commit 5b622ce
committed
Provide a bit more accurate "reason" for debug stop.
It turns out that when the debugger stops at a function breakpoint, it isn't necessarily obvious why the debugger stopped. There is no breakpoint glyph for a function breakpoint. So if we return "function breakpoint", then VSCode will display "PAUSED ON FUNCTION BREAKPOINT" in the call stack viewlet. Hopefully that will help the user know why the debugger stopped.1 parent 3bd9a26 commit 5b622ce
File tree
1 file changed
+16
-1
lines changed- src/PowerShellEditorServices.Protocol/Server
1 file changed
+16
-1
lines changedLines changed: 16 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
474 | 474 | | |
475 | 475 | | |
476 | 476 | | |
| 477 | + | |
| 478 | + | |
| 479 | + | |
| 480 | + | |
| 481 | + | |
| 482 | + | |
| 483 | + | |
| 484 | + | |
| 485 | + | |
| 486 | + | |
| 487 | + | |
| 488 | + | |
| 489 | + | |
| 490 | + | |
| 491 | + | |
477 | 492 | | |
478 | 493 | | |
479 | 494 | | |
| |||
485 | 500 | | |
486 | 501 | | |
487 | 502 | | |
488 | | - | |
| 503 | + | |
489 | 504 | | |
490 | 505 | | |
491 | 506 | | |
| |||
0 commit comments