From 163f70be9d87960fb260eb5c03383799f78b46b5 Mon Sep 17 00:00:00 2001 From: Jeff Lucovsky Date: Thu, 17 Jun 2021 09:04:56 -0400 Subject: [PATCH] logging: Stacktrace on signal term setting This commit adds a configuration setting to enable a stack trace message if Suricata receives a signal that terminates execution, such as SIGSEGV, SIGABRT. --- suricata.yaml.in | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/suricata.yaml.in b/suricata.yaml.in index f779904711..50c559bc19 100644 --- a/suricata.yaml.in +++ b/suricata.yaml.in @@ -544,6 +544,11 @@ logging: # This value is overridden by the SC_LOG_OP_FILTER env var. default-output-filter: + # Requires libunwind to be available when Suricata is configured and built. + # If a signal unexpectedly terminates Suricata, displays a brief diagnostic + # message with the offending stacktrace if enabled. + #stacktrace-on-signal: on + # Define your logging outputs. If none are defined, or they are all # disabled you will get the default: console output. outputs: