Project

General

Profile

Actions
Copy link

Feature #4526

closed

SIGSEGV handling -- log stack before aborting

Added by Jeff Lucovsky over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jeff Lucovsky
Target version:
7.0.0-beta1
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 2 (0 open — 2 closed)

Related to Suricata - Bug #5070: Stacktrace logger should propagate original signalClosedJeff LucovskyActions
Copied to Suricata - Feature #4973: SIGSEGV handling -- log stack before abortingClosedJeff LucovskyActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky over 3 years ago

  • Status changed from New to In Review
  • Assignee set to Jeff Lucovsky
Actions
Copy link
 #2

Updated by Jeff Lucovsky almost 3 years ago

  • Status changed from In Review to Closed
Actions
Copy link
 #3

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Feature #4973: SIGSEGV handling -- log stack before aborting added
Actions
Copy link
 #4

Updated by Jeff Lucovsky over 2 years ago

  • Related to Bug #5070: Stacktrace logger should propagate original signal added
Actions
Copy link

Also available in: Atom PDF