Project

General

Profile

Actions

Feature #4973

closed

SIGSEGV handling -- log stack before aborting

Added by Jeff Lucovsky about 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

Not all deployment scenarios are equipped to assist troubleshooting efforts and hence, core files are not always possible.

In some environments, a stack trace can be used to assist troubleshooting.

The general approach would be to
- Install a SIGSEGV handler
- Use libunwind to gather and log (to stderr minimally) the stacktrace.


Related issues 1 (0 open1 closed)

Copied from Suricata - Feature #4526: SIGSEGV handling -- log stack before abortingClosedJeff LucovskyActions
Actions

Also available in: Atom PDF