---
** [tickets:#1281] base: Dump stack trace to file on fatal signals**
**Status:** assigned
**Milestone:** 4.7-Tentative
**Created:** Tue Mar 24, 2015 10:05 AM UTC by Anders Widell
**Last Updated:** Tue Mar 24, 2015 10:05 AM UTC
**Owner:** hano
Sometimes, core dumps are either lost or difficult to analyze, for example
because the binaries and/or libraries that were used at the time of the fault
are no longer available.
To aid trouble shooting in such cases, the suggestion is to install a signal
handler for fatal signals (SIGHUP, SIGILL, SIGABRT, SIGFPE, SIGSEGV, SIGPIPE,
SIGALARM, SIGTERM, SIGBUS). The signal handler should open a file and dump the
stack trace to that file, and then re-raise the signal to continue standard
signal handling. It should also check if the signal was sent by another
process, and in that case dump the identity of the sender.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
