From da505f84d3e8fc3bb7c54fea76eb5574987ee01a Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Wed, 6 Nov 2019 11:39:02 +0100 Subject: pkg/report: detect syzkaller panics in lost connection bugs Some syzkaller panics happen due to memory corruptions, but it still would be useful at least to get some visibility into these crashes. On some OSes we actualy already detect them as they have "panic:" oops pattern, but not e.g. on linux. Fixes #318 --- pkg/report/fuchsia.go | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-) (limited to 'pkg/report/fuchsia.go') diff --git a/pkg/report/fuchsia.go b/pkg/report/fuchsia.go index 25facf658..df64055e4 100644 --- a/pkg/report/fuchsia.go +++ b/pkg/report/fuchsia.go @@ -185,7 +185,7 @@ var zirconStackParams = &stackParams{ }, } -var zirconOopses = []*oops{ +var zirconOopses = append([]*oops{ { []byte("ZIRCON KERNEL PANIC"), []oopsFormat{ @@ -316,17 +316,4 @@ var zirconOopses = []*oops{ compile("<== fatal exception: process .+?syz.+?\\["), }, }, - { - // Panics in Go services. - []byte("panic: "), - []oopsFormat{ - { - title: compile("panic: .*"), - report: compile("panic: (.*)(?:.*\\n)+?.* goroutine"), - fmt: "panic: %[1]v", - noStackTrace: true, - }, - }, - []*regexp.Regexp{}, - }, -} +}, commonOopses...) -- cgit mrf-deployment