Reconsider meaning/behavior of "no trace" fatal assertions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • 135
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Fatal assertions have both a vanilla version and a "no trace" version. The former uses std::abort while the latter uses quickExit with ExitCode::abrupt. In some cases it does make sense to not log a backtrace, for instance if the user starts up the server on unsupported data files. However we also won't capture a core dump in this case, even if the system is set up to capture them upon unclean shutdown. This can make diagnosis difficult if the conditions leading to the (no trace) fatal assertion were unexpected.

              Assignee:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: