cmd/compile: gdb 8 on windows crashes reading Go binary #21380

kjk · 2017-08-10T03:55:19Z

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

> go version
go version go1.9rc2 windows/amd64

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

> go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\kjk\src\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
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

What did you do?

I'm trying to gather more information on #20975 which involves running the executable on windows under a debugger that understands dwarf debug info (because neither msvc nor windbg do).

I tried:

clone repro program https://github.com/kjk/go20975 and run build.ps1 to build it
download gdb from https://nuwen.net/mingw.html and unpack under c:\
run C:\MinGW\bin\gdb.exe .\go20975.exe to run under dbg
enter https://vox.com in text box

What did you expect to see?

When crash happens, I expected to get a human-readable callstack.

What did you see instead?

[New Thread 2176.0xc90]
fatal: morestack on g0
../../src/gdb/buildsym.c:1773: internal-error: void buildsym_init(): Assertion `free_pendings == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

The crash happened in the program but it also crashed gdb.

It seems that DWARF information created by Go compiler breaks gdb.

PS C:\Users\kjk\src\go\src\github.com\kjk\go20975> C:\MinGW\bin\gdb.exe --version
GNU gdb (GDB) 8.0

The text was updated successfully, but these errors were encountered:

kjk · 2017-08-10T04:41:02Z

The same happens for gdb 7.11.1 from http://www.msys2.org/

[New Thread 7596.0x1398]
fatal: morestack on g0
buildsym.c:1773: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

$ gdb --version
GNU gdb (GDB) 7.11.1

mvdan · 2017-08-10T07:53:53Z

@kjk if this worked with 1.8 and if you have the time, bisecting this to a commit made during the 1.9 cycle would be of great help.

alexbrainman · 2017-08-11T01:57:10Z

This works for me with GNU gdb (GDB) 7.8 and go version devel +6b6b9f69fd Wed Aug 9 05:33:09 2017 +0000 windows/amd64.
I don't have skills or time to debug gdb.

Alex

tobiaskohlbau · 2017-08-14T06:16:40Z

I'm also on windows and encountered a similar behavior when compiling go from source. The tests TestGdbBacktrace and TestGdbAutompTypes fail to run after compilation, with the exact same internal gdb error as posted here. After the suggestion by Alex Brainman that gdb 7.8 works for him I downloaded an old gdb and was able to confirm this on my machine. In the first try I got GNU gdb (GDB) 7.9.1 which states in the release notes:

Changes in this release include:
Python scripting enhancements.
Source code compilation and injection into the inferior.
New commands, options, convenience variables/options.
MIPS SDE support (mips*-sde*-elf*).
Better handling of signals when debugging threaded programs.

Within the go documentation there exists the comment that go makes use of a extension for gdb. As I'm not familiar with GDB and the extension possibility I would like to give this information as a starting point for other people to debug this error.

Edit: As suggested by mvdan I tried to build 1.8 release branch but got the exact same problem. So it's not a bug which was introduced by go 1.9 itself.

kjk · 2017-08-26T02:00:06Z

Just noting that some dwarf fix, not necessarily related, was made: 38bd725

dsnet · 2017-09-01T23:21:17Z

Go 1.9 has since been released. Is this still an issue? Unfortunately, this was not placed in the right milestone, so it slipped through triaging.

tobiaskohlbau · 2017-09-02T22:22:36Z

I've pulled the latest changes (03c3bb5) and retried this issue. It's still failing with the same error:

--- FAIL: TestGdbAutotmpTypes (2.12s)
        runtime-gdb_test.go:55: gdb version 7.12
        runtime-gdb_test.go:379: could not find struct []main.astruct; in 'info typrs astruct' output
        runtime-gdb_test.go:380: gdb output:
                No symbol "startup" in current context.
                ../../gdb-7.12/gdb/buildsym.c:1773: internal-error: void 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/>.

                ../../gdb-7.12/gdb/buildsym.c:1773: internal-error: void 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: TestGdbBacktrace (2.56s)
        runtime-gdb_test.go:55: gdb version 7.12
        runtime-gdb_test.go:310: could not find '#0.*main\.eee' in backtrace
        runtime-gdb_test.go:311: gdb output:
                No symbol "startup" in current context.
                ../../gdb-7.12/gdb/buildsym.c:1773: internal-error: void 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/>.

                ../../gdb-7.12/gdb/buildsym.c:1773: internal-error: void 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.

thanm · 2017-09-13T12:53:22Z

FYI, it looks as though a GDB binutils bug, 18624 was filed back in 2015 for this same issue. Reported for GDB 7.9, but presumably with a version of Go that was a good deal older than 1.9. This would suggest that the problem is not specific to 1.9.

rsc · 2017-10-13T18:36:55Z

Given that this has been happening since 2015, not for Go 1.9.2.

dis2 · 2018-03-18T04:20:39Z

For anyone tripping on this: A temporary workaround is to use external linker:

go build -ldflags=-linkmode=external

This seems to make gdb happy (at least on recent windows/msys2)

gopherbot · 2018-03-24T16:33:00Z

Change https://golang.org/cl/102419 mentions this issue: runtime: improve Windows gdb tests

This ensures that gdb tests run on Windows by ignoring any line ending. Works with gdb 7.7, however with gdb 7.9 and 7.12 gets an error error: internal-error: buildsym_init: Assertion `free_pendings == NULL' failed. Updates #21380 Change-Id: I6a6e5b2a1b5efdca4dfce009fcb9c134c87497d6 Reviewed-on: https://go-review.googlesource.com/102419 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>

kjk · 2018-06-29T20:45:45Z

This still happens with gdb 8.1 and go 1.11 (trunk).

I've provided more details in gdb bug tracker: https://sourceware.org/bugzilla/show_bug.cgi?id=18624#c9

kjk · 2018-06-29T21:21:57Z

This might be a gdb bug that only happens with COFF/PE: https://sourceware.org/ml/gdb-patches/2018-06/msg00736.html

timou · 2019-03-29T18:12:32Z

I believe this is fixed in gdb 8.2. It now passes for me using STL's excellent and most recent MinGW distribution.

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4735f0edf4265e3e260e10a12921baf17987a020

C:\Code\go\src\runtime>go test -test.v -test.run=.*TestGdbBacktrace
=== RUN   TestGdbBacktrace
=== PAUSE TestGdbBacktrace
=== CONT  TestGdbBacktrace
--- PASS: TestGdbBacktrace (0.81s)
    runtime-gdb_test.go:66: gdb version 8.2
PASS
ok      runtime 0.880s

C:\Code\go\src\runtime>gdb -version
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

dajoo75 · 2019-03-30T08:27:56Z

I'm just gonna leave this here for any poor soul on Windows who installs/updates MinGW and friends once in a blue moon or so: https://stackoverflow.com/questions/30069830/how-to-install-mingw-w64-and-msys2

gopherbot · 2023-02-23T13:26:52Z

Change https://go.dev/cl/470596 mentions this issue: runtime: set procid on Windows

The runtime-gdb.py script needs procid to be set in order to map a goroutine ID with an OS thread. The Go runtime is not currently setting that variable on Windows, so TestGdbPython (and friends) can't succeed. This CL initializes procid and unskips gdb tests on Windows. Fixes #22687 Updates #21380 Updates #22021 Change-Id: Icd1d9fc1764669ed1bf04f53d17fadfd24ac3f30 Reviewed-on: https://go-review.googlesource.com/c/go/+/470596 Reviewed-by: Alex Brainman <alex.brainman@gmail.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Quim Muntal <quimmuntal@gmail.com>

golang deleted a comment Aug 26, 2017

dsnet added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 1, 2017

dsnet added this to the Go1.9.1 milestone Sep 1, 2017

ianlancetaylor added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Sep 9, 2017

rsc modified the milestones: Go1.9.1, Go1.9.2 Oct 4, 2017

rsc modified the milestones: Go1.9.2, Go1.10 Oct 13, 2017

rsc changed the title ~~go 1.9rc2 windows/amd64 breaks gdb 8~~ cmd/compile: gdb 8 on windows crashes reading Go binary Oct 13, 2017

thanm modified the milestones: Go1.10, Go1.11 Nov 29, 2017

ALTree added the OS-Windows label Mar 24, 2018

alexbrainman mentioned this issue Apr 7, 2018

runtime: TestGdbAutotmpTypes fails on windows #24743

Closed

ianlancetaylor removed this from the Go1.11 milestone Jun 30, 2018

ianlancetaylor added this to the Go1.12 milestone Jun 30, 2018

AlexRouSg mentioned this issue Nov 10, 2018

cmd/go: compatibility problems on Windows #28697

Closed

andybons modified the milestones: Go1.12, Go1.13 Feb 12, 2019

timou mentioned this issue Mar 29, 2019

gdb.exe crashing on golang 1.7rc3 unit test TestGdbBacktrace StephanTLavavej/mingw-distro#24

Closed

andybons modified the milestones: Go1.13, Go1.14 Jul 8, 2019

rsc modified the milestones: Go1.14, Backlog Oct 9, 2019

bcmills mentioned this issue May 21, 2020

runtime: move tests for runtime-gdb.py to a separate package and do not run them during all.bash #39204

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cmd/compile: gdb 8 on windows crashes reading Go binary #21380

cmd/compile: gdb 8 on windows crashes reading Go binary #21380

kjk commented Aug 10, 2017

kjk commented Aug 10, 2017 •

edited

mvdan commented Aug 10, 2017

alexbrainman commented Aug 11, 2017

tobiaskohlbau commented Aug 14, 2017 •

edited

kjk commented Aug 26, 2017

dsnet commented Sep 1, 2017

tobiaskohlbau commented Sep 2, 2017

thanm commented Sep 13, 2017

rsc commented Oct 13, 2017

dis2 commented Mar 18, 2018

gopherbot commented Mar 24, 2018

kjk commented Jun 29, 2018

kjk commented Jun 29, 2018

timou commented Mar 29, 2019 •

edited

dajoo75 commented Mar 30, 2019 •

edited

gopherbot commented Feb 23, 2023

cmd/compile: gdb 8 on windows crashes reading Go binary #21380

cmd/compile: gdb 8 on windows crashes reading Go binary #21380

Comments

kjk commented Aug 10, 2017

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

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

What did you do?

What did you expect to see?

What did you see instead?

kjk commented Aug 10, 2017 • edited

mvdan commented Aug 10, 2017

alexbrainman commented Aug 11, 2017

tobiaskohlbau commented Aug 14, 2017 • edited

kjk commented Aug 26, 2017

dsnet commented Sep 1, 2017

tobiaskohlbau commented Sep 2, 2017

thanm commented Sep 13, 2017

rsc commented Oct 13, 2017

dis2 commented Mar 18, 2018

gopherbot commented Mar 24, 2018

kjk commented Jun 29, 2018

kjk commented Jun 29, 2018

timou commented Mar 29, 2019 • edited

dajoo75 commented Mar 30, 2019 • edited

gopherbot commented Feb 23, 2023

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

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

kjk commented Aug 10, 2017 •

edited

tobiaskohlbau commented Aug 14, 2017 •

edited

timou commented Mar 29, 2019 •

edited

dajoo75 commented Mar 30, 2019 •

edited