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

runtime: access violation in gentraceback on windows/386 #50144

Open
bcmills opened this issue Dec 13, 2021 · 11 comments
Open

runtime: access violation in gentraceback on windows/386 #50144

bcmills opened this issue Dec 13, 2021 · 11 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. OS-Windows
Milestone

Comments

@bcmills
Copy link
Member

bcmills commented Dec 13, 2021

#!watchflakes
post <- builder ~ `windows` && `fatal error: unexpected signal during runtime execution\n\[signal 0xc0000005 .*` && `^runtime\.gentraceback`

greplogs --dashboard -md -l -e '(?ms)^fatal error: unexpected signal during runtime execution\n\[signal 0xc0000005.*^runtime\.gentraceback'

2021-12-13T18:45:54-2580d0e/windows-386-2012

##### ../misc/cgo/test
PASS
scatter = 01199220
sqrt is: 0
hello from C
ok  	misc/cgo/test	15.271s
PASS
scatter = 00402290
sqrt is: 0
hello from C
ok  	misc/cgo/test	14.725s
PASS
scatter = 01409220
sqrt is: 0
hello from C
ok  	misc/cgo/test	15.264s
PASS
scatter = 013C9220
sqrt is: 0
hello from C
ok  	misc/cgo/test	14.413s
Exception 0x200c7 0xf0030de8 0xcc483ff 0x0
PC=0x0

fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x12399a4]

runtime stack:
runtime.throw({0x136e0a5, 0x2a})
	C:/workdir/go/src/runtime/panic.go:992 +0x64 fp=0x3540f9ec sp=0x3540f9d8 pc=0x1217394
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:249 +0x26d fp=0x3540fa10 sp=0x3540f9ec pc=0x122bf0d
runtime.gentraceback(0x0, 0x0, 0x0, 0x134002d0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:94 +0x154 fp=0x3540fbfc sp=0x3540fa10 pc=0x12399a4
runtime.traceback1(0x0, 0x0, 0x0, 0x134002d0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:835 +0x1a2 fp=0x3540fcdc sp=0x3540fbfc pc=0x123bf82
runtime.tracebacktrap(0x0, 0x0, 0x0, 0x134002d0)
	C:/workdir/go/src/runtime/traceback.go:799 +0x7e fp=0x3540fcf4 sp=0x3540fcdc pc=0x123bdce
runtime.winthrow(0x1315baa, 0x13433a80, 0x134002d0)
	C:/workdir/go/src/runtime/signal_windows.go:234 +0x202 fp=0x3540fd20 sp=0x3540fcf4 pc=0x122b8e2
runtime.lastcontinuehandler(0x1315baa, 0x13433a80, 0x134002d0)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x3540fd30 sp=0x3540fd20 pc=0x122b6c8
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x3540fd34 sp=0x3540fd30 pc=0x12458c7

goroutine 17 [running, locked to thread]:
fatal error: unexpected signal during runtime execution
panic during panic
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x1239e7c]

runtime stack:
runtime.throw({0x136e0a5, 0x2a})
	C:/workdir/go/src/runtime/panic.go:992 +0x64 fp=0x3540f658 sp=0x3540f644 pc=0x1217394
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:249 +0x26d fp=0x3540f67c sp=0x3540f658 pc=0x122bf0d
runtime.gentraceback(0xffffffff, 0xffffffff, 0x0, 0x134002d0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x0)
	C:/workdir/go/src/runtime/traceback.go:232 +0x62c fp=0x3540f868 sp=0x3540f67c pc=0x1239e7c
runtime.traceback1(0xffffffff, 0xffffffff, 0x0, 0x134002d0, 0x0)
	C:/workdir/go/src/runtime/traceback.go:835 +0x1a2 fp=0x3540f948 sp=0x3540f868 pc=0x123bf82
runtime.traceback(...)
	C:/workdir/go/src/runtime/traceback.go:782
runtime.tracebackothers(0x134001e0)
	C:/workdir/go/src/runtime/traceback.go:1027 +0x8f fp=0x3540f978 sp=0x3540f948 pc=0x123cc1f
runtime.dopanic_m(0x134001e0, 0x1217394, 0x3540f9d8)
	C:/workdir/go/src/runtime/panic.go:1192 +0x23f fp=0x3540f9a0 sp=0x3540f978 pc=0x1217b1f
runtime.fatalthrow.func1()
	C:/workdir/go/src/runtime/panic.go:1047 +0x4b fp=0x3540f9c0 sp=0x3540f9a0 pc=0x12175fb
runtime.fatalthrow()
	C:/workdir/go/src/runtime/panic.go:1044 +0x5a fp=0x3540f9d8 sp=0x3540f9c0 pc=0x121759a
runtime.throw({0x136e0a5, 0x2a})
	C:/workdir/go/src/runtime/panic.go:992 +0x64 fp=0x3540f9ec sp=0x3540f9d8 pc=0x1217394
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:249 +0x26d fp=0x3540fa10 sp=0x3540f9ec pc=0x122bf0d
runtime.gentraceback(0x0, 0x0, 0x0, 0x134002d0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:94 +0x154 fp=0x3540fbfc sp=0x3540fa10 pc=0x12399a4
runtime.traceback1(0x0, 0x0, 0x0, 0x134002d0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:835 +0x1a2 fp=0x3540fcdc sp=0x3540fbfc pc=0x123bf82
runtime.tracebacktrap(0x0, 0x0, 0x0, 0x134002d0)
	C:/workdir/go/src/runtime/traceback.go:799 +0x7e fp=0x3540fcf4 sp=0x3540fcdc pc=0x123bdce
runtime.winthrow(0x1315baa, 0x13433a80, 0x134002d0)
	C:/workdir/go/src/runtime/signal_windows.go:234 +0x202 fp=0x3540fd20 sp=0x3540fcf4 pc=0x122b8e2
runtime.lastcontinuehandler(0x1315baa, 0x13433a80, 0x134002d0)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x3540fd30 sp=0x3540fd20 pc=0x122b6c8
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x3540fd34 sp=0x3540fd30 pc=0x12458c7
*** Test killed: ran too long (11m0s).
exit status 1
FAIL	misc/cgo/test	660.032s

2021-10-29T17:13:13-645d078/windows-386-2008
2020-12-22T20:00:00-c9fb4eb/windows-386-2008
2020-03-25T14:19:25-91b8b13/windows-386-2008

@bcmills
Copy link
Member Author

bcmills commented Dec 13, 2021

CC @bufflig @alexbrainman @cherrymui

At first I thought this might have something to do with #49681, but some of the failures are much older.

@cherrymui
Copy link
Member

cherrymui commented Dec 13, 2021

Yeah, this looks different from #49681 . It looks like it panics again while printing traceback from a fault.

@bufflig
Copy link
Contributor

bufflig commented Dec 13, 2021

Is the fact that is prints "Test killed: ran too long" relevant? I mean is this something that happens when we try to kill the test, or does the test end up in an infinite loop?

@cherrymui cherrymui added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows labels Dec 13, 2021
@cherrymui cherrymui added this to the Backlog milestone Dec 13, 2021
@bcmills
Copy link
Member Author

bcmills commented Dec 14, 2021

I mean is this something that happens when we try to kill the test, or does the test end up in an infinite loop?

Not clear to me. It may be that this failure mode tends to occur when the signal terminating the test arrives on top of another signal or vice-versa — that would at least explain the presence of the gentraceback in the stack.

The Test killed: ran too long message comes from here:
https://cs.opensource.google/go/go/+/master:src/cmd/go/internal/test/test.go;l=1397-1412;drc=7bdbc73be1d10a9b32cb5edc6b9d0c93805f059c

That suggests that perhaps the binary did deadlock after printing the panic during panic stack.

@bcmills
Copy link
Member Author

bcmills commented May 11, 2022

greplogs -l -e '(?ms)^fatal error: unexpected signal during runtime execution\n\[signal 0xc0000005.*^runtime\.gentraceback' --since=2021-12-14
2022-05-10T23:13:45-f12461c/windows-386-2008

(CC @golang/windows @golang/runtime)

@bcmills bcmills changed the title runtime: access violation in gentraceback on Windows runtime: access violation in gentraceback on windows/386 May 11, 2022
@cherrymui
Copy link
Member

cherrymui commented May 13, 2022

It looks like the traceback is called with PC=SP=LR=0. It faults when it tries to read from the SP. Maybe the signal context is wrong? I search for exception 0x200c7 but couldn't find anything useful. So perhaps the exception code is also wrong?

Perhaps the exception handler shouldn't be called in the first place? I don't know what caused it to be called (with seemingly wrong arguments).

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
@bcmills
Copy link
Member Author

bcmills commented Aug 22, 2022

2022-08-08T14:11:19-6e9925c/windows-386-2012:

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
Exception 0xc7 0xcccccccc 0xcccccccc 0x0
PC=0x0

fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x465d7a]

runtime stack:
runtime.throw({0x7f14e7, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x328ffbdc sp=0x328ffbc8 pc=0x44047d
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:250 +0x23b fp=0x328ffc00 sp=0x328ffbdc pc=0x455fab
runtime.gentraceback(0x0, 0x0, 0x0, 0x142ca4b0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:95 +0x16a fp=0x328ffe10 sp=0x328ffc00 pc=0x465d7a
runtime.traceback1(0x0, 0x0, 0x0, 0x142ca4b0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:846 +0x1a2 fp=0x328ffef0 sp=0x328ffe10 pc=0x468562
runtime.tracebacktrap(0x0, 0x0, 0x0, 0x142ca4b0)
	C:/workdir/go/src/runtime/traceback.go:810 +0x7e fp=0x328fff08 sp=0x328ffef0 pc=0x4683ae
runtime.winthrow(0x750df4, 0x12860ad0, 0x142ca4b0)
	C:/workdir/go/src/runtime/signal_windows.go:235 +0x202 fp=0x328fff34 sp=0x328fff08 pc=0x4559b2
runtime.lastcontinuehandler(0x750df4, 0x12860ad0, 0x142ca4b0)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x328fff44 sp=0x328fff34 pc=0x455798
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x328fff48 sp=0x328fff44 pc=0x477657

goroutine 136158 [running]:
fatal error: unexpected signal during runtime execution
panic during panic
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x46631f]

runtime stack:
runtime.throw({0x7f14e7, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x328ff824 sp=0x328ff810 pc=0x44047d
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:250 +0x23b fp=0x328ff848 sp=0x328ff824 pc=0x455fab
runtime.gentraceback(0xffffffff, 0xffffffff, 0x0, 0x142ca4b0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x0)
	C:/workdir/go/src/runtime/traceback.go:236 +0x70f fp=0x328ffa58 sp=0x328ff848 pc=0x46631f
runtime.traceback1(0xffffffff, 0xffffffff, 0x0, 0x142ca4b0, 0x0)
	C:/workdir/go/src/runtime/traceback.go:846 +0x1a2 fp=0x328ffb38 sp=0x328ffa58 pc=0x468562
runtime.traceback(...)
	C:/workdir/go/src/runtime/traceback.go:793
runtime.tracebackothers(0x14502000)
	C:/workdir/go/src/runtime/traceback.go:1038 +0x8f fp=0x328ffb68 sp=0x328ffb38 pc=0x46921f
runtime.dopanic_m(0x14502000, 0x44047d, 0x328ffbc8)
	C:/workdir/go/src/runtime/panic.go:1271 +0x22f fp=0x328ffb90 sp=0x328ffb68 pc=0x440cef
runtime.fatalthrow.func1()
	C:/workdir/go/src/runtime/panic.go:1125 +0x4b fp=0x328ffbb0 sp=0x328ffb90 pc=0x4407cb
runtime.fatalthrow(0x2)
	C:/workdir/go/src/runtime/panic.go:1122 +0x6b fp=0x328ffbc8 sp=0x328ffbb0 pc=0x44076b
runtime.throw({0x7f14e7, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x328ffbdc sp=0x328ffbc8 pc=0x44047d
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:250 +0x23b fp=0x328ffc00 sp=0x328ffbdc pc=0x455fab
runtime.gentraceback(0x0, 0x0, 0x0, 0x142ca4b0, 0x0, 0x0, 0x64, 0x0, 0x0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:95 +0x16a fp=0x328ffe10 sp=0x328ffc00 pc=0x465d7a
runtime.traceback1(0x0, 0x0, 0x0, 0x142ca4b0, 0x2)
	C:/workdir/go/src/runtime/traceback.go:846 +0x1a2 fp=0x328ffef0 sp=0x328ffe10 pc=0x468562
runtime.tracebacktrap(0x0, 0x0, 0x0, 0x142ca4b0)
	C:/workdir/go/src/runtime/traceback.go:810 +0x7e fp=0x328fff08 sp=0x328ffef0 pc=0x4683ae
runtime.winthrow(0x750df4, 0x12860ad0, 0x142ca4b0)
	C:/workdir/go/src/runtime/signal_windows.go:235 +0x202 fp=0x328fff34 sp=0x328fff08 pc=0x4559b2
runtime.lastcontinuehandler(0x750df4, 0x12860ad0, 0x142ca4b0)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x328fff44 sp=0x328fff34 pc=0x455798
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x328fff48 sp=0x328fff44 pc=0x477657
*** Test killed: ran too long (6m0s).
FAIL	runtime	360.016s

@gopherbot
Copy link

gopherbot commented Oct 4, 2022

Found new dashboard test flakes for:

#!watchflakes
post <- builder ~ `windows` && `fatal error: unexpected signal during runtime execution\n\[signal 0xc0000005 .*` && `^runtime\.gentraceback`
2022-09-02 19:09 windows-arm64-10 go@55ca6a20 runtime/trace.TestTraceCPUProfile (log)
fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x7ff6f49eb8e4]

runtime stack:
runtime.throw({0x7ff6f4b4c65b?, 0x0?})
	C:/workdir/go/src/runtime/panic.go:1047 +0x40 fp=0xea793ff1b0 sp=0xea793ff180 pc=0x7ff6f49c73a0
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:251 +0x220 fp=0xea793ff200 sp=0xea793ff1b0 pc=0x7ff6f49dcc90
runtime.gentraceback(0x4000041520?, 0x4000024000?, 0xea793ff5a8?, 0x40003c4000, 0x0, 0xea793ff5a8, 0x40, 0x0, 0x0?, 0x6)
	C:/workdir/go/src/runtime/traceback.go:162 +0x304 fp=0xea793ff540 sp=0xea793ff210 pc=0x7ff6f49eb8e4
...
	C:/workdir/go/src/runtime/trace/trace_test.go:774 +0x74 fp=0x40002759a0 sp=0x4000275970 pc=0x7ff6f4af3934
runtime/trace_test.cpuHog1(0x0?)
	C:/workdir/go/src/runtime/trace/trace_test.go:766 +0x24 fp=0x40002759c0 sp=0x40002759a0 pc=0x7ff6f4af3894
runtime/trace_test.cpuHogger(0x7ff6f4b51038, 0x7ff6f4cdfec8, 0x5f5e100)
	C:/workdir/go/src/runtime/trace/trace_test.go:753 +0x54 fp=0x4000275a10 sp=0x40002759c0 pc=0x7ff6f4af37e4
runtime/trace_test.TestTraceCPUProfile.func1(0x5f5e100)
	C:/workdir/go/src/runtime/trace/trace_test.go:618 +0x1f8 fp=0x4000275af0 sp=0x4000275a10 pc=0x7ff6f4af3688
runtime/trace_test.TestTraceCPUProfile(0x400040d380)
	C:/workdir/go/src/runtime/trace/trace_test.go:619 +0x12c fp=0x4000275f60 sp=0x4000275af0 pc=0x7ff6f4af283c
testing.tRunner(0x400040d380, 0x7ff6f4b50fc0)
2022-09-05 08:08 windows-amd64-longtest go@af7f4176 runtime/pprof.TestMathBigDivide (log)
fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x3ac66f]

runtime stack:
runtime.throw({0x51017b?, 0x5e6150?})
	C:/workdir/go/src/runtime/panic.go:1047 +0x65 fp=0x69bd3fed18 sp=0x69bd3fece8 pc=0x388645
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:251 +0x213 fp=0x69bd3fed60 sp=0x69bd3fed18 pc=0x39d453
runtime.gentraceback(0xffffffdccc0fa9c0?, 0x69bd3ff130?, 0x8?, 0xc000052820, 0x0, 0x69bd3ff130, 0x40, 0x0, 0x0?, 0x6)
	C:/workdir/go/src/runtime/traceback.go:162 +0x4cf fp=0x69bd3ff0d0 sp=0x69bd3fed60 pc=0x3ac66f
...
	C:/workdir/go/src/math/big/int.go:250 +0x9c fp=0xc00029bda8 sp=0xc00029bd20 pc=0x4909fc
math/big.(*Int).Div(0xc00029be80?, 0xc00029be60?, 0xc00029be40?)
	C:/workdir/go/src/math/big/int.go:261 +0x45 fp=0xc00029be08 sp=0xc00029bda8 pc=0x490b25
runtime/pprof.TestMathBigDivide.func1(0x54c760?)
	C:/workdir/go/src/runtime/pprof/pprof_test.go:752 +0x125 fp=0xc00029beb0 sp=0xc00029be08 pc=0x4bf2e5
runtime/pprof.testCPUProfile(0xc000604340, 0xc00029bf60?, 0x517440)
	C:/workdir/go/src/runtime/pprof/pprof_test.go:465 +0x1da fp=0xc00029bf48 sp=0xc00029beb0 pc=0x4aacfa
runtime/pprof.TestMathBigDivide(0xc000085380?)
	C:/workdir/go/src/runtime/pprof/pprof_test.go:745 +0x25 fp=0xc00029bf70 sp=0xc00029bf48 pc=0x4ac825
testing.tRunner(0xc000604340, 0x517448)
2022-09-27 15:57 windows-386-2012 go@e978ef36 runtime (log)
Exception 0xc7 0xcccccccc 0xcccccccc 0x0
PC=0x0

fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x4652b9]

runtime stack:
runtime.throw({0x8026a2, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x2c10fbd8 sp=0x2c10fbc4 pc=0x43f45d
runtime.sigpanic()
...
fatal error: unexpected signal during runtime execution
panic during panic
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x46590f]

runtime stack:
runtime.throw({0x8026a2, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x2c10f81c sp=0x2c10f808 pc=0x43f45d
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:251 +0x23b fp=0x2c10f840 sp=0x2c10f81c pc=0x4552ab
runtime.gentraceback(0xffffffff, 0xffffffff, 0x0, 0xd77fd10, 0x0, 0x0, 0x64, 0x0, 0x0, 0x0)
...
	C:/workdir/go/src/runtime/traceback.go:764 +0x1a7 fp=0x2c10fef0 sp=0x2c10fe10 pc=0x4678d7
runtime.tracebacktrap(0x0, 0x0, 0x0, 0xd77fd10)
	C:/workdir/go/src/runtime/traceback.go:728 +0x7e fp=0x2c10ff08 sp=0x2c10fef0 pc=0x46771e
runtime.winthrow(0x75e284, 0xb381ad0, 0xd77fd10)
	C:/workdir/go/src/runtime/signal_windows.go:236 +0x221 fp=0x2c10ff34 sp=0x2c10ff08 pc=0x454cb1
runtime.lastcontinuehandler(0x75e284, 0xb381ad0, 0xd77fd10)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x2c10ff44 sp=0x2c10ff34 pc=0x454a78
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x2c10ff48 sp=0x2c10ff44 pc=0x4797f7
*** Test killed: ran too long (6m0s).

watchflakes

@qmuntal
Copy link
Contributor

qmuntal commented Oct 21, 2022

Last watchflake report in previous comment seems to be conflating two different bugs. Both windows-amd64 builders have a nil pointer exception in gentraceback while dereferencing gp.m:

if flags&_TraceJumpStack != 0 && gp == gp.m.g0 && gp.m.curg != nil && gp.m.curg.m == gp.m {

windows-386 builder has a different failure more, also in gentraceback, which I haven't identified.

I don't know how gp.m could be nil, but a nil check wouldn't do any harm, just as it is done in other places within gentraceback.

@gopherbot
Copy link

gopherbot commented Oct 21, 2022

Change https://go.dev/cl/444618 mentions this issue: runtime: check for nil gp.m in gentraceback.go

@gopherbot
Copy link

gopherbot commented Oct 25, 2022

Found new dashboard test flakes for:

#!watchflakes
post <- builder ~ `windows` && `fatal error: unexpected signal during runtime execution\n\[signal 0xc0000005 .*` && `^runtime\.gentraceback`
2022-10-24 17:28 windows-386-2008 go@0cc20ecc runtime (log)
Exception 0xc7 0xcccccccc 0xcccccccc 0x0
PC=0x0

fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x465dda]

runtime stack:
runtime.throw({0x7f172f, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x335efbe4 sp=0x335efbd0 pc=0x4404ad
runtime.sigpanic()
...
fatal error: unexpected signal during runtime execution
panic during panic
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x46637f]

runtime stack:
runtime.throw({0x7f172f, 0x2a})
	C:/workdir/go/src/runtime/panic.go:1047 +0x4d fp=0x335ef82c sp=0x335ef818 pc=0x4404ad
runtime.sigpanic()
	C:/workdir/go/src/runtime/signal_windows.go:249 +0x23f fp=0x335ef850 sp=0x335ef82c pc=0x455fcf
runtime.gentraceback(0xffffffff, 0xffffffff, 0x0, 0x128a3e00, 0x0, 0x0, 0x64, 0x0, 0x0, 0x0)
...
	C:/workdir/go/src/runtime/traceback.go:846 +0x1a2 fp=0x335efef8 sp=0x335efe18 pc=0x4685c2
runtime.tracebacktrap(0x0, 0x0, 0x0, 0x128a3e00)
	C:/workdir/go/src/runtime/traceback.go:810 +0x7e fp=0x335eff10 sp=0x335efef8 pc=0x46840e
runtime.winthrow(0x750ed4, 0x12a2dad0, 0x128a3e00)
	C:/workdir/go/src/runtime/signal_windows.go:234 +0x202 fp=0x335eff3c sp=0x335eff10 pc=0x4559d2
runtime.lastcontinuehandler(0x750ed4, 0x12a2dad0, 0x128a3e00)
	C:/workdir/go/src/runtime/signal_windows.go:198 +0x58 fp=0x335eff4c sp=0x335eff3c pc=0x4557b8
sigtramp()
	C:/workdir/go/src/runtime/sys_windows_386.s:127 +0x77 fp=0x335eff50 sp=0x335eff4c pc=0x477737
*** Test killed: ran too long (6m0s).

watchflakes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. OS-Windows
Projects
Status: Triage Backlog
Status: No status
Development

No branches or pull requests

5 participants