Project

General

Profile

Actions
Copy link

Bug #5070

closed

Stacktrace logger should propagate original signal

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

Status:
Closed
Priority:
Normal
Assignee:
Jeff Lucovsky
Target version:
7.0.0-beta1
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 open — 2 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
Copy link
 #1

Updated by Jeff Lucovsky almost 3 years ago

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

Updated by Jeff Lucovsky almost 3 years ago

  • Status changed from New to In Review
  • Assignee changed from OISF Dev to Jeff Lucovsky
Actions
Copy link
 #3

Updated by Jeff Lucovsky almost 3 years ago

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

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Bug #5097: Stacktrace logger should propagate original signal added
Actions
Copy link
 #5

Updated by Jeff Lucovsky almost 3 years ago

  • Target version changed from TBD to 7.0.0-beta1
Actions
Copy link

Also available in: Atom PDF