「view this page in B3 βῆτα server」

Revisions №60867

branch: master 「№60867」
Commited by: Rocco Moretti
GitHub commit link: 「2e1b6f9e2fa46734」 「№4074」
Difference from previous tested commit:  code diff
Commit date: 2019-08-13 15:25:54
linux.clang linux.gcc linux.srlz mac.clang
debug
release
unit
linux.PyRosetta.unit linux.gcc.python37.PyRosetta4.unit mac.PyRosetta.unit build.clean.debug cppcheck mysql postgres linux.clang.python36.build.debug linux.zeromq.debug mpi mpi.serialization linux.icc.build.debug OpenCL mac.clang.python36.build.debug build.header build.levels ninja graphics static linux.ui mac.ui build.xcode beautification code_quality.clang_analysis serialization integration.mpi integration.release_debug integration.thread integration performance profile release.source scientific.mp_symdock.debug linux.clang.score linux.gcc.score mac.clang.score linux.scripts.pyrosetta scripts.rosetta.parse scripts.rosetta.validate scripts.rosetta.verify linux.clang.unit.release linux.gcc.unit.release util.apps

Merge pull request #4074 from RosettaCommons/roccomoretti/crash_display_change Adjust the application signature for new crash reporter scheme. The crash reporter PR (#2978) introduces a slight change in how exceptions should be handled in executables. Instead of the application displaying the message itself, it should call the Exception::display() function, which will handle doing the appropriate display (and any applicable crash report generation). Most of this is just somewhat mechanical changes to the source/src/apps files. (I've also updated the code templates) But I also have changes to the JD2 & JD3 exception handling, such that errors which are caught by the JD machinery will also generate the appropriate logs.