Project

General

Profile

Feature #8171

Improve the messages for cet::exception

Added by Krzysztof Genser over 4 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/25/2015
Due date:
% Done:

0%

Estimated time:
Scope:
Internal
Experiment:
-
SSI Package:
Co-Assignees:
Duration:

Description

Could the cet::exception messages be made more informative?
eg. a function/stack and line number info of the original exception be added?
(epsecially given that gdb will not be able to provide that info since the program exits "cleanly")

%MSG-e PassingThrough: PostSourceRun 25-Mar-2015 09:33:53 CDT run: 1
an exception occurred during current event processing

%MSG
%MSG-s ArtException: PostCloseFile 25-Mar-2015 09:33:54 CDT run: 1
cet::exception caught in art
---- StdException BEGIN
The EventProcessor caught a std::exception and converted it to a cet::exception
Previous information:
map::at
---- StdException END
%MSG


Related issues

Related to cetlib_except - Feature #14795: Traceback printout on fatal exceptions would be niceAccepted2016-12-09

Is duplicate of art - Idea #918: Add architecture-specific capture of call stack at time of construction of cet::exception.Accepted

History

#1 Updated by Christopher Green over 4 years ago

  • Is duplicate of Idea #918: Add architecture-specific capture of call stack at time of construction of cet::exception. added

#2 Updated by Christopher Green over 4 years ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Accepted

This is a long standing issue that we have not been able to schedule.

In the meantime, the normal way to trace this problem is to (e.g. for gdb)

catch throw
. The debugger will then stop at the point the exception is thrown, and bt or where will have gdb provide the full stack trace to the exception throw point.

#3 Updated by Kyle Knoepfel over 4 years ago

  • Target version set to 521

#4 Updated by Kyle Knoepfel over 2 years ago

  • Related to Feature #14795: Traceback printout on fatal exceptions would be nice added

#5 Updated by Kyle Knoepfel over 1 year ago

  • Target version deleted (521)


Also available in: Atom PDF