Fixes #16063: Enable backtrace in relayd

Normation · Oct 25, 2019 · bdbc31b · bdbc31b
1 parent 50bf22b
commit bdbc31b
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 10 deletions.
diff --git a/relay/sources/relayd/Cargo.lock b/relay/sources/relayd/Cargo.lock
diff --git a/relay/sources/relayd/fuzz/Cargo.lock b/relay/sources/relayd/fuzz/Cargo.lock
diff --git a/relay/sources/relayd/src/relayd.rs b/relay/sources/relayd/src/relayd.rs
@@ -31,7 +31,7 @@
 use relayd::{
     check_configuration, configuration::cli::CliConfiguration, error::Error, init_logger, start,
 };
-use std::process::exit;
+use std::{env, process::exit};
 use structopt::StructOpt;
 use tracing::error;
 
@@ -45,6 +45,12 @@ fn error_code(e: &Error) -> i32 {
 
 /// Everything in a lib to allow extensive testing
 fn main() {
+    // https://www.reddit.com/r/rust/comments/bnqina/why_does_not_rust_give_a_backtrace_by_default/
+    // https://internals.rust-lang.org/t/rust-backtrace-in-production-use/5609/2
+    // May be expensive only when backtraces are actually produced
+    // and can be helpful to troubleshoot production crashes
+    env::set_var("RUST_BACKTRACE", "1");
+
     let cli_cfg = CliConfiguration::from_args();
     if cli_cfg.check_configuration {
         if let Err(ref e) = check_configuration(&cli_cfg.configuration_dir) {