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

runtime: TestGdbAutotmpTypes fails on windows #24743

Closed
alexbrainman opened this issue Apr 7, 2018 · 1 comment
Closed

runtime: TestGdbAutotmpTypes fails on windows #24743

alexbrainman opened this issue Apr 7, 2018 · 1 comment
Labels
FrozenDueToAge

Comments

@alexbrainman
Copy link
Member

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

go version devel +31db81d329 Fri Apr 6 23:03:41 2018 +0000 windows/amd64

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

set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Alex\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\users\alex\dev
set GORACE=
set GOROOT=c:\users\alex\dev\go
set GOTMPDIR=
set GOTOOLDIR=c:\users\alex\dev\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
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
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\Alex\AppData\Local\Temp\go-build725076794=/tmp/go-build -gno-record-gcc-switches

What did you do?

I installed gdb from http://tdm-gcc.tdragon.net/

gcc (tdm64-1) 5.1.0
GNU gdb (GDB) 7.9.1

and then I run

go test -run=Gdb runtime

command

What did you expect to see?

I expected tests to pass.

What did you see instead?

I see test failed with

c:\>go test -run=Gdb runtime
--- FAIL: TestGdbAutotmpTypes (0.64s)
        runtime-gdb_test.go:59: gdb version 7.9
        runtime-gdb_test.go:414: could not find struct []main.astruct; in 'info typrs astruct' output
        runtime-gdb_test.go:415: gdb output:
                warning: File "c:\users\alex\dev\go\src\runtime\runtime-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
                To enable execution of this file add
                        add-auto-load-safe-path c:\users\alex\dev\go\src\runtime\runtime-gdb.py
                line to your configuration file "$HOME/.gdbinit".
                To completely disable this security protection add
                        set auto-load safe-path /
                line to your configuration file "$HOME/.gdbinit".
                For more information about this security protection see the
                "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
                        info "(gdb)Auto-loading safe path"
                No symbol "startup" in current context.
                C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.
                A problem internal to GDB has been detected,
                further debugging may prove unreliable.
                Quit this debugging session? (y or n) [answered Y; input not from terminal]

                This is a bug, please report it.  For instructions, see:
                <http://www.gnu.org/software/gdb/bugs/>.

                C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.
                A problem internal to GDB has been detected,
                further debugging may prove unreliable.
                Create a core file of GDB? (y or n) [answered Y; input not from terminal]

                This application has requested the Runtime to terminate it in an unusual way.
                Please contact the application's support team for more information.
--- FAIL: TestGdbConst (0.67s)
        runtime-gdb_test.go:59: gdb version 7.9
        runtime-gdb_test.go:472: output "warning: File \"c:\\users\\alex\\dev\\go\\src\\runtime\\runtime-gdb.py\" auto-loading has been declined by your `auto-load safe-path' set to \"$debugdir:$datadir/auto-load\".\nTo enable execution of this file add\n\tadd-auto-load-safe-path c:\\users\\alex\\dev\\go\\src\\runtime\\runtime-gdb.py\nline to your configuration file \"$HOME/.gdbinit\".\nTo completely disable this security protection add\n\tset auto-load safe-path /\nline to your configuration file \"$HOME/.gdbinit\".\nFor more information about this security protection see the\n\"Auto-loading safe path\" section in the GDB manual.  E.g., run from the shell:\n\tinfo \"(gdb)Auto-loading safe path\"\nNo symbol \"startup\" in current context.\nC:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? (y or n) [answered Y; input not from terminal]\n\nThis is a bug, please report it.  For instructions, see:\n<http://www.gnu.org/software/gdb/bugs/>.\n\nC:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreate a core file of GDB? (y or n) [answered Y; input not from terminal]\n\nThis application has requested the Runtime to terminate it in an unusual way.\nPlease contact the application's support team for more information.\n"
        runtime-gdb_test.go:475: output mismatch
--- FAIL: TestGdbBacktrace (0.68s)
        runtime-gdb_test.go:59: gdb version 7.9
        runtime-gdb_test.go:345: could not find '#0.*main\.eee' in backtrace
        runtime-gdb_test.go:346: gdb output:
                warning: File "c:\users\alex\dev\go\src\runtime\runtime-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
                To enable execution of this file add
                        add-auto-load-safe-path c:\users\alex\dev\go\src\runtime\runtime-gdb.py
                line to your configuration file "$HOME/.gdbinit".
                To completely disable this security protection add
                        set auto-load safe-path /
                line to your configuration file "$HOME/.gdbinit".
                For more information about this security protection see the
                "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
                        info "(gdb)Auto-loading safe path"
                No symbol "startup" in current context.
                C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.
                A problem internal to GDB has been detected,
                further debugging may prove unreliable.
                Quit this debugging session? (y or n) [answered Y; input not from terminal]

                This is a bug, please report it.  For instructions, see:
                <http://www.gnu.org/software/gdb/bugs/>.

                C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1759: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.
                A problem internal to GDB has been detected,
                further debugging may prove unreliable.
                Create a core file of GDB? (y or n) [answered Y; input not from terminal]

                This application has requested the Runtime to terminate it in an unusual way.
                Please contact the application's support team for more information.
FAIL
FAIL    runtime 0.863s

c:\>

Alex
@alexbrainman alexbrainman mentioned this issue Apr 7, 2018
Open
@alexbrainman
Copy link
Member Author

Oops. This is just a dup of #21380. Closing.

Alex

@golang golang locked and limited conversation to collaborators Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gopherbot @alexbrainman