Project

General

Profile

Actions
Copy link

Feature #4973

closed

SIGSEGV handling -- log stack before aborting

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

Status:
Closed
Priority:
Normal
Assignee:
Jeff Lucovsky
Target version:
6.0.5
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 open — 1 closed)

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

Updated by Jeff Lucovsky almost 3 years ago

  • Copied from Feature #4526: SIGSEGV handling -- log stack before aborting added
Actions
Copy link
 #2

Updated by Jeff Lucovsky almost 3 years ago

  • Status changed from Assigned to In Progress

Cherry-pick commit(s):
- 303dd29
- 501c870
- 163f70b
- 7f0f463
- 93842aa

Actions
Copy link
 #3

Updated by Jeff Lucovsky almost 3 years ago

  • Status changed from In Progress to In Review
Actions
Copy link
 #4

Updated by Shivani Bhardwaj over 2 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF