Project

General

Profile

Actions

Bug #5070

closed

Stacktrace logger should propagate original signal

Added by Jeff Lucovsky 8 months ago. Updated 6 months 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 Feature #4526: SIGSEGV handling -- log stack before abortingClosedJeff LucovskyActions
Copied to Bug #5097: Stacktrace logger should propagate original signalClosedJeff LucovskyActions
Actions #1

Updated by Jeff Lucovsky 8 months ago

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

Updated by Jeff Lucovsky 8 months ago

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

Updated by Jeff Lucovsky 8 months ago

  • Status changed from In Review to Closed
Actions #4

Updated by Jeff Lucovsky 8 months ago

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

Updated by Jeff Lucovsky 7 months ago

  • Target version changed from TBD to 7.0rc1
Actions

Also available in: Atom PDF