Commit f64d05b
committed
fix: reset "stopOnEntry" after first use to show correct pause reason (#478)
* Reset "stopOnEntry" after first use to show correct pause reason.
If "stopOnEntry" is enabled the pause reason will always be "Paused on entry" event if it's the result of a step operation or breakpoint. Resetting the "stopOnEntry" after first use solves the issue. The flag is not used anywhere else.
* Do not use _args.stopOnEntry since it should be regarded immutable and is set only on every adapter run.
Reconnecting to adapter would cause issues.
Always reset _hasStoppedOnEntry flag just before calling the step into operation.1 parent 4e1e1fe commit f64d05b
1 file changed
+6
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
140 | 140 | | |
141 | 141 | | |
142 | 142 | | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
143 | 146 | | |
144 | 147 | | |
145 | 148 | | |
| |||
363 | 366 | | |
364 | 367 | | |
365 | 368 | | |
366 | | - | |
| 369 | + | |
367 | 370 | | |
| 371 | + | |
368 | 372 | | |
369 | 373 | | |
370 | 374 | | |
| |||
623 | 627 | | |
624 | 628 | | |
625 | 629 | | |
| 630 | + | |
626 | 631 | | |
627 | 632 | | |
628 | 633 | | |
| |||
0 commit comments