From: Jeff Lucovsky <jeff@lucovsky.org>
Date: Thu, 17 Jun 2021 13:04:56 +0000 (-0400)
Subject: logging: Stacktrace on signal term setting
X-Git-Tag: suricata-7.0.0-beta1~1091
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=163f70be9d87960fb260eb5c03383799f78b46b5;p=thirdparty%2Fsuricata.git

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.
---

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: