Project

General

Profile

Actions

Bug #5070

closed

Stacktrace logger should propagate original signal

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

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0

Description

The stack-trace on signal feature https://redmine.openinfosecfoundation.org/issues/4526 raises SIGABRT after creating the log entry.

Instead, it should raise the actual signal (SIGSEGV or SIGABRT) for better monitoring/reporting of actual problems.


Related issues 2 (0 open2 closed)

Related to Suricata - Feature #4526: SIGSEGV handling -- log stack before abortingClosedJeff LucovskyActions
Copied to Suricata - Bug #5097: Stacktrace logger should propagate original signalClosedJeff LucovskyActions
Actions

Also available in: Atom PDF