Skip to content
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

Jump to bottom

cmd/compile: debugger jumps around declarations #32786

Open
dlsniper opened this issue Jun 26, 2019 · 2 comments
Open

cmd/compile: debugger jumps around declarations #32786

dlsniper opened this issue Jun 26, 2019 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@dlsniper
Copy link
Contributor

What version of Go are you using (go version)?

$ go version
go version devel +9bf62783d2 Wed Jun 26 06:27:56 2019 +0000 windo
ws/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output 
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\florin\AppData\Local\go-build
set GOENV=C:\Users\florin\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=D:\go
set GOPRIVATE=
set GOPROXY=direct
set GOROOT=C:\go-master
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\go-master\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\go-samples\debugging\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-m
ap=C:\Users\florin\AppData\Local\Temp\go-build286245954=/tmp/go-b
uild -gno-record-gcc-switches

What did you do?

b main.go:38
c
n
n
n
n
n
n

What did you expect to see?

I would expect the execution pointer to follow the code and step thru the structure construction as it's defined in the code.

What did you see instead?

The execution pointer randomly jumps around, like in this video https://youtu.be/0FcDOg5ez4o (and it happens from command line as well as GoLand so it's not an implementation issue for the UI)
@dlsniper
Copy link
Contributor Author

I remember @dr2chase and @heschik were interested in such cases, so please have a look. Thank you!

@dr2chase dr2chase added this to the Go1.14 milestone Jun 26, 2019
@dr2chase dr2chase self-assigned this Jun 26, 2019
@dr2chase
Copy link
Contributor

I'll put my name on this for now, but won't be working on it for some time yet because of 1.13 release cycle stuff.

@rsc rsc modified the milestones: Go1.14, Backlog Oct 9, 2019
@cagedmantis cagedmantis changed the title Debugger jumps around declarations cmd/compile: debugger jumps around declarations Jun 24, 2022
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 24, 2022
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Compiler / Runtime
Status: Triage Backlog
Milestone
Backlog
Development

No branches or pull requests
5 participants
@rsc @cagedmantis @dlsniper @dr2chase @gopherbot