932aad9e3d
next/step/stepout should work even if the current frame isn't the topmost stack frame, but their behavior should be different in that case (they should continue inside the function of the selected frame). Most of the logic of next/step/stepout would work correctly if we simply replaced the call to proc.topframe with something that took a frame index. However the breakpoint they set on the first deferred function is wrong, and fixing it requires scanning the defer stack and matching it to the call stack, something we can't do yet. Given that enhancing next/step/stepout will take time and the current behavior confuses users (see issue #1240) return an error if next/step/stepout are called while the currently selected frame isn't frame 0. Updates #1240 |
||
|---|---|---|
| .. | ||
| command_test.go | ||
| command.go | ||
| config.go | ||
| disasmprint.go | ||
| docgen.go | ||
| terminal_other.go | ||
| terminal_test.go | ||
| terminal_windows.go | ||
| terminal.go | ||