delve/_fixtures/issue1656/main.s

#include "textflag.h"

TEXT ·compromised(SB),NOSPLIT,$0-8
	CMPQ n+0(FP), $0
	JNZ notzero
	RET
notzero:
	MOVQ $0, AX
	MOVQ $1, AX
	CALL main·skipped(SB)
	RET
proc: next/step/stepout restarts thread from wrong instruction (#1657) proc.Next and proc.Step will call, after setting their temp breakpoints, curthread.SetCurrentBreakpoint. This is intended to find if one of the newly created breakpoints happens to be at the same instruction that curthread is stopped at. However SetCurrentBreakpoint is intended to be called after a Continue and StepInstruction operation so it will also detect if curthread is stopped one byte after a breakpoint. If the instruction immediately preceeding the current instruction of curthread happens to: 1. have one of the newly created temp breakpoints 2. be one byte long SetCurrentBreakpoint will believe that we just hit that breakpoint and therefore the instruction should be repeated, and thus rewind the PC of curthread by 1. We should distinguish between the two uses of SetCurrentBreakpoint and disable the check for "just hit" breakpoints when inappropriate. Fixes #1656 2019-08-12 22:11:19 +00:00			`#include "textflag.h"`

			`TEXT ·compromised(SB),NOSPLIT,$0-8`
			`CMPQ n+0(FP), $0`
			`JNZ notzero`
			`RET`
			`notzero:`
			`MOVQ $0, AX`
			`MOVQ $1, AX`
			`CALL main·skipped(SB)`
			`RET`