-
Notifications
You must be signed in to change notification settings - Fork 18.7k
Description
--- FAIL: TestLineFromAline (0.00s)
panic: runtime error: slice bounds out of range [76:68] [recovered]
panic: runtime error: slice bounds out of range [76:68]
goroutine 20 [running]:
testing.tRunner.func1.2({0x81b3d60, 0xa176680})
/workdir/go/src/testing/testing.go:1209 +0x2ab
testing.tRunner.func1(0xa0825a0)
/workdir/go/src/testing/testing.go:1212 +0x27d
panic({0x81b3d60, 0xa176680})
/workdir/go/src/runtime/panic.go:1038 +0x1c5
golang.org/x/vuln/vulncheck/internal/gosym.funcData.funcdataOffset({0xa0a60a0, {0xa240480, 0x44, 0x44}}, 0x3)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab.go:584 +0x127
golang.org/x/vuln/vulncheck/internal/gosym.(*LineTable).go12Funcs(0xa0a60a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab.go:373 +0x1f6
golang.org/x/vuln/vulncheck/internal/gosym.NewTable({0x82ebda0, 0x0, 0x0}, 0xa0a60a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/symtab.go:519 +0x5f1
golang.org/x/vuln/vulncheck/internal/gosym.parse({0xffb79ccc, 0x2f}, 0xa0f6180, 0xa0825a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab_test.go:82 +0x3d7
golang.org/x/vuln/vulncheck/internal/gosym.crack({0xffb79ccc, 0x2f}, 0xa0825a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab_test.go:62 +0xae
golang.org/x/vuln/vulncheck/internal/gosym.getTable(0xa0825a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab_test.go:51 +0x42
golang.org/x/vuln/vulncheck/internal/gosym.TestLineFromAline(0xa0825a0)
/workdir/gopath/src/golang.org/x/vuln/vulncheck/internal/gosym/pclntab_test.go:94 +0x32
testing.tRunner(0xa0825a0, 0x81cd5d0)
/workdir/go/src/testing/testing.go:1259 +0xe6
created by testing.(*T).Run
/workdir/go/src/testing/testing.go:1306 +0x33a
FAIL golang.org/x/vuln/vulncheck/internal/gosym 0.009s
FAIL
greplogs --dashboard -md -l -e 'FAIL: TestLineFromAline .*(?:\n.*)*panic: runtime error: slice bounds out of range' --since=2022-01-01
2022-04-07T17:51:26-1784cc9-7139e8b/freebsd-386-11_4
2022-04-07T17:51:26-1784cc9-7139e8b/freebsd-386-12_3
2022-04-07T17:51:26-1784cc9-7139e8b/freebsd-386-13_0
2022-04-07T17:51:26-1784cc9-7139e8b/linux-386
2022-04-07T17:51:26-1784cc9-7139e8b/linux-386-buster
2022-04-07T17:51:26-1784cc9-7139e8b/linux-386-clang
2022-04-07T17:51:26-1784cc9-7139e8b/linux-386-sid
2022-04-07T17:51:26-1784cc9-7139e8b/linux-386-stretch
2022-04-07T17:51:26-1784cc9-7139e8b/linux-arm-aws
2022-04-07T17:51:26-1784cc9-7139e8b/netbsd-386-9_0
2022-04-07T17:51:26-1784cc9-7139e8b/openbsd-386-68
2022-04-07T17:51:26-1784cc9-7139e8b/openbsd-386-70
This failure mode appears to have been introduced in CL 398755 (attn @jba; CC @golang/security). It isn't obvious to me why it wasn't caught by the TryBots for that CL.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status