Issue 9217 in go: runtime: failed initialization of GODEBUG vars

[g...@googlecode.com]

Status: New
Owner: ----

New issue 9217 by cooki...@gmail.com: runtime: failed initialization of
GODEBUG vars
https://code.google.com/p/go/issues/detail?id=9217

At tip on windows/amd64, setting GODEBUG options causes the following panic:

> set GODEBUG=gctrace=1
> go version
[signal 0xc0000005 code=0x1 addr=0x0 pc=0x49a7df]

runtime stack:
runtime.gothrow(0x921f50, 0x2a)
C:/go-tip/src/runtime/panic.go:507 +0x98 fp=0x7fdc0 sp=0x7fda8
runtime.sigpanic()
C:/go-tip/src/runtime/os_windows.go:16 +0x65 fp=0x7fde8 sp=0x7fdc0
runtime.parsedebugvars()
C:/go-tip/src/runtime/runtime1.go:334 +0x2bf fp=0x7fee8 sp=0x7fde8
runtime.schedinit()
C:/go-tip/src/runtime/proc1.go:124 +0x71 fp=0x7ff30 sp=0x7fee8
runtime.rt0_go(0x7ff60, 0x7fffb61c16ad, 0x7ff60, 0x0, 0x7fffb61c16ad, 0x0,
0x0, 0x0, 0x0, 0x0, ...)
C:/go-tip/src/runtime/asm_amd64.s:96 +0x124 fp=0x7ff38 sp=0x7ff30

When the GODEBUG variable is cleared:
> set GODEBUG=
> go version
go version devel +2d1ab17a670a Fri Dec 05 21:33:07 2014 -0500 windows/amd64

I have tried several different values for GODEBUG:
- GODEBUG=gctrace=0 (PANIC)
- GODEBUG=allocfreetrace=1 (PANIC)
- GODEBUG=allocfreetrace=1,gctrace=1 (PANIC)
- GODEBUG=x=2 (NO PANIC)
- GODEBUG=gctrace=1,x=2 (PANIC)

It looks like it only happens when valid debug vars are present in GODEBUG.

The issue is also present in windows/386. I have not tested elsewhere.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[g...@googlecode.com]

Comment #1 on issue 9217 by mi...@golang.org: runtime: failed

initialization of GODEBUG vars
https://code.google.com/p/go/issues/detail?id=9217

known problem for 1.5, but still investigating the proper fix.
see https://codereview.appspot.com/172510043/