From 1306dbf268f7940ccdcf1b8a58af259a1b918b52 Mon Sep 17 00:00:00 2001 From: Jeff Lucovsky Date: Thu, 17 Jun 2021 09:24:46 -0400 Subject: [PATCH] doc/yaml: Signal-termination option description (cherry picked from commit 93842aa14a67ed1e7acfc6bbdacbffef8bd6bae0) --- doc/userguide/configuration/suricata-yaml.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index 6a4db36f01..cb62523169 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -2246,6 +2246,21 @@ inspected for possible presence of Teredo. Advanced Options ---------------- +stacktrace +~~~~~~~~~~ +Display diagnostic stacktraces when a signal unexpectedly terminates Suricata, e.g., such as +SIGSEGV or SIGABRT. Requires the ``libunwind`` library to be available. The default value is +to display the diagnostic message if a signal unexpectedly terminates Suricata -- e.g., +``SIGABRT`` or ``SIGSEGV`` occurs while Suricata is running. + +:: + + logging: + # 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 + luajit ~~~~~~ -- 2.47.2