-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger stops at breakpoint in a loop only once (Windows Arm64) #3183
Comments
cc @qmuntal |
Also |
I think it's fine to continue here. |
Thanks for reporting this issue. I'll investigate it next week. |
Which version of go are you using @sergunya? Can't reproduce this issue with |
@qmuntal hey, |
I'm afraid I can't reproduce this locally. I do have an OS build slightly newer than yours ( |
Delve version 1.24 (with exp. flag set), Go 1.23, Windows 11 24H2 Arm64. Time has passed, now it works excellent, stops in the loop everytime. Tested in vs code, not command line though. Thanks for the install command line :-) |
1. dlv version
2. go version
go version go1.19.3 windows/arm64
3. Operating system and processor architecture
6. Steps to reproduce
Install delve for Windows arm64
go install -tags exp.winarm64 github.com/go-delve/delve/cmd/dlv
Create sample.go file with the outlined below content
`package main
import (
"fmt"
)
func main() {
length, capacity, y := 1000, 2000, 3
AllResults := make([]int, length, capacity)
for i := 0; i < length; i++ {
result := i / y // Hi there
fmt.Println(result)
AllResults[i] = result
}
j := 0
fmt.Println(j)
}`
Start debug client:
dlv debug sample.go
Add breakpoint inside loop:
(dlv) break sample.go:12
Continue debug session
(dlv) continue
(debugger stops at breakpoint)Continue debug session further
(dlv) continue
7. Expected result
The debugger stops at the breakpoint in every cycle in a loop.
8. Actual result
The debugger stops at the breakpoint only in first cycle of the loop.
The text was updated successfully, but these errors were encountered: