exceptions handling: small improvements

It is better to avoid empty catches when we have a reasonable way
to log an (even unlikely) exception, even more so if memory
allocations are involved.

1 files changed, 5 insertions, 2 deletions

diff --git a/src/other_tools/just_mr/setup_utils.cpp b/src/other_tools/just_mr/setup_utils.cpp
index 43d19709..915efe08 100644
--- a/src/other_tools/just_mr/setup_utils.cpp
+++ b/src/other_tools/just_mr/setup_utils.cpp
@@ -230,8 +230,11 @@ auto ReadConfiguration(
 
     try {
         return std::make_shared<Configuration>(Expression::FromJson(config));
-    } catch (...) {
-        return nullptr;
+    } catch (std::exception const& e) {
+        Logger::Log(LogLevel::Error,
+                    "Parsing configuration file failed with error:\n{}",
+                    e.what());
+        std::exit(kExitConfigError);
     }
 }