Project

General

Profile

Actions
Copy link

Feature #446

closed

dump stack to log on segfault

Added by Sage Weil over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Yehuda Sadeh
Category:
-
Target version:
v0.23
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Should be doable if we trap SIGSEG?

One thing to keep in mind is that the common/assert.cc code currently deliberately does a segfault to induce a core dump. There is probably a better way to go about it.

Actions
Copy link
 #1

Updated by Yehuda Sadeh over 13 years ago

  • Assignee set to Yehuda Sadeh
Actions
Copy link
 #2

Updated by Yehuda Sadeh over 13 years ago

Commit:3e56ac4b377a3f39f040556beffb7c58cc2baea4 adds the signal handling part. Need to decide whether we keep the current assert code that dumps the backtrace or not.

Actions
Copy link
 #3

Updated by Yehuda Sadeh over 13 years ago

  • Status changed from New to Resolved

We'll keep the backtrace in the assertion code for now. Commit:e064796bea3985c088e74f75f35637225827bab8 adds some info about the caught signal, so that it's more clear when reading the assertion log.

Actions
Copy link

Also available in: Atom PDF