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 f779904711ab6c883d54889ef8f50f22e03963cd..50c559bc19cac52053b308ceb68a88e03f5eaae1 100644 (file)
--- 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: