From f1bbaaa0bb2a52a3bebb2ac75527a795a8d41a72 Mon Sep 17 00:00:00 2001 From: Greg Steuck Date: Mon, 29 Aug 2022 11:29:55 +0200 Subject: pkg/report: use `show panic` output for unscrambled panic message The original panic: is printed without logging and is often garbled by concurrent printing by another core. OTOH, `show panic` is printed exclusively so we prefer to use that. --- pkg/report/openbsd.go | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'pkg/report/openbsd.go') diff --git a/pkg/report/openbsd.go b/pkg/report/openbsd.go index dc2970c76..13e5a5136 100644 --- a/pkg/report/openbsd.go +++ b/pkg/report/openbsd.go @@ -39,6 +39,10 @@ var openbsdOopses = append([]*oops{ { []byte("panic:"), []oopsFormat{ + { + title: compile(`\nddb\{\d+\}> show panic(?Us:.*)[*]cpu\d+: ([^\n]+)(?Us:.*)\nddb\{\d+\}> trace`), + fmt: "panic: %[1]v", + }, { title: compile("panic: kernel diagnostic assertion (.+) failed: file \".*/([^\"]+)"), fmt: "assert %[1]v failed in %[2]v", -- cgit mrf-deployment