Traceback printout on fatal exceptions would be nice

[knoepfel]

This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/14795 (FNAL account required)
Originally created by @tomjunk on 2016-12-09 20:51:59

---

Using art services that throw fatal cet::exceptions can create some difficult-to-debug situations in which we know what crashed, but we do not know what called it (without starting a debugger). When a fatal exception is thrown, but before the stack is unwound, it would be nice to print out a backtrace, however ugly. Extra credit for being able to turn this feature on and off.

---

Related issues:

• Add architecture-specific capture of call stack at time of construction of cet::exception. art#8
• https://cdcvs.fnal.gov/redmine/issues/8171 (FNAL account required)

[knoepfel]

Comment by @knoepfel on 2016-12-19 17:55:14

---

We will propose a solution at the next stakeholder meeting. Capturing the call-stack information can be expensive at run-time, and if we are going to do this, we need to have agreement from the stakeholders that the cost is worth it. We will also discuss mechanisms for run-time control of the facility.