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
go version devel +18fb670 Tue May 2 00:21:33 2017 +0000 windows/386
What operating system and processor architecture are you using (go env)?
set GOARCH=386
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=386
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\dev
set GORACE=
set GOROOT=c:\dev\go
set GOTOOLDIR=c:\dev\go\pkg\tool\windows_386
set GCCGO=gccgo
set GO386=
set CC=gcc
set GOGCCFLAGS=-m32 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\DOCUME1\brainman\LOCALS1\Temp\go-build677740063=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
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
Maybe debug.go, hashmap.go, slice.go, string.go, error.go, iface.go or print.go... these should be included most of the time? Alternatively, add a file specifically for it?
Also, when you have a my/package/runtime/runtime.go the current approach could use the wrong thing.
Maybe debug.go, hashmap.go, slice.go, string.go, error.go, iface.go or print.go... these should be included most of the time? Alternatively, add a file specifically for it?
Also, when you have a my/package/runtime/runtime.go the current approach could use the wrong thing.
I am not sure what the right approach is. But we need new test to check that .debug_gdb_scripts is included in the exe.
What version of Go are you using (
go version
)?go version devel +18fb670 Tue May 2 00:21:33 2017 +0000 windows/386
What operating system and processor architecture are you using (
go env
)?set GOARCH=386
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=386
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\dev
set GORACE=
set GOROOT=c:\dev\go
set GOTOOLDIR=c:\dev\go\pkg\tool\windows_386
set GCCGO=gccgo
set GO386=
set CC=gcc
set GOGCCFLAGS=-m32 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\DOCUME
1\brainman\LOCALS1\Temp\go-build677740063=/tmp/go-build -gno-record-gcc-switchesset CXX=g++
set CGO_ENABLED=1
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
What did you do?
I built this program:
and listed executable file sections with:
What did you expect to see?
What did you see instead?
I see the above output, but without .debug_gdb_scripts section present.
I checked the .debug_gdb_scripts section is present on linux. In fact, if I make this change:
I see this (on linux):
which explains why it does not work on windows - there is no syscall.runtime_envs on windows.
Looking for suggestion what to look for in finddebugruntimepath so it works on windows too. Thank you.
Alex
The text was updated successfully, but these errors were encountered: