Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

log/diag: Support diagnostic stacktraces on SIGSEGV #6200

Closed
wants to merge 6 commits into from
Closed

log/diag: Support diagnostic stacktraces on SIGSEGV #6200

wants to merge 6 commits into from

Commits on Jun 17, 2021

  1. configure.ac: Support libunwind configuration 

    This commit adds support for enabling libunwind -- a library that can be
used to display stack information.

Use --enable-libunwind to check for availability. A diagnostic message
is displayed if libunwind cannot be found as requested.
    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    e74438f View commit details
    Browse the repository at this point in the history

  2. error: Add error code for SIGSEGV diagnostic 

    This commit adds an error code for the diagnostic code used for SIGSEGV
diagnostic messages.
    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    8413db5 View commit details
    Browse the repository at this point in the history

  3. logging: Stacktrace on SIGSEGV setting 

    This commit adds a configuration setting to enable a stack trace message
if Suricata receives a SIGSEGV.
    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    7f49b73 View commit details
    Browse the repository at this point in the history

  4. logging/diag: Enable stacktrace diagnostic if config'd 

    This commit adds a signal handler for SIGSEGV when configured. The
signal handler emits a one line stack trace using SCLogError. The intent
is to provide diagnostic information in deployments where core files are
not possible.

The diagnostic message is from the offending thread and includes the
stack trace; each frame includes the symbol + offset.
    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    a2958ee View commit details
    Browse the repository at this point in the history

  5. general: Fix typo

    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    f1e2ed7 View commit details
    Browse the repository at this point in the history

  6. doc/yaml: SIGSEGV option description

    @jlucovsky
    jlucovsky committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    49ad5cd View commit details
    Browse the repository at this point in the history