-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Open
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.compiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.
Milestone
Description
#!watchflakes
post <- pkg == "runtime" && test ~ `TestSegv` && `schedule: holding locks`
Issue created automatically to collect these failures.
Example (log):
--- FAIL: TestSegv (0.00s)
--- FAIL: TestSegv/SegvInCgo (0.01s)
crash_cgo_test.go:656: /tmp/workdir/tmp/go-build2656727872/testprogcgo.exe SegvInCgo: exit status 2
crash_cgo_test.go:657: fatal error: schedule: holding locks
SIGSEGV: segmentation violation
PC=0x3e4d5f m=4 sigcode=65537 addr=0x0
goroutine 1 gp=0xc0000061c0 m=4 mp=0xc000088008 [syscall]:
syscall.Syscall(0x25, 0x2af3, 0xb, 0x0)
/tmp/workdir/go/src/syscall/asm_unix_amd64.s:19 +0x9 fp=0xc000065e20 sp=0xc000065e10 pc=0x3e4d49
...
r13 0x1
r14 0xc0000061c0
r15 0x3
rip 0x3e4d5f
rflags 0x206
cs 0x43
fs 0x13
gs 0x1b
crash_cgo_test.go:688: unexpectedly saw "fatal error: " in output
Metadata
Metadata
Assignees
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.compiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.
Type
Projects
Status
Todo
Status
No status