You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The statement marker for line 15 ends up on instruction 0x487748, a JMP, instead of 0x48774a. But the program reaches that line from another path that jumps directly to 0x48774a. Specifically through: 0x487734 → 0x48775a → 0x48774a.
What version of Go are you using (
go version
)?but also devel at c043fc4 (newest as of today)
What did you do?
Take this program:
compile with
go build -gcflags='-N -l' onajmp.go
, then:(or use delve+break+continue, exact same thing).
The breakpoint on line 15 (the call to main.h) gets skipped entirely.
Why
The statement marker for line 15 ends up on instruction 0x487748, a JMP, instead of 0x48774a. But the program reaches that line from another path that jumps directly to 0x48774a. Specifically through: 0x487734 → 0x48775a → 0x48774a.
@gopherbot, please add label Debugging
cc @heschik @dr2chase
The text was updated successfully, but these errors were encountered: