Feature #14795
Traceback printout on fatal exceptions would be nice
Status:
Accepted
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12/09/2016
Due date:
% Done:
0%
Estimated time:
Experiment:
DUNE
SSI Package:
cetlib
Categorization:
-
Description
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
History
#1 Updated by Kyle Knoepfel over 3 years ago
- Related to Idea #918: Add architecture-specific capture of call stack at time of construction of cet::exception. added
#2 Updated by Kyle Knoepfel over 3 years ago
- Related to Feature #8171: Improve the messages for cet::exception added
#3 Updated by Kyle Knoepfel over 3 years ago
- Status changed from New to Accepted
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.