Searched full:rust_backtrace (Results 1 – 25 of 25) sorted by relevance
50 RUST_BACKTRACE: full54 RUST_BACKTRACE: full
4 Subject: [PATCH] Support RUST_BACKTRACE settings in test_fmt6 Setting `RUST_BACKTRACE` when running tests is useful so that the logs
59 Sometimes a backtrace may be needed. In that case, set `RUST_BACKTRACE`63 $ RUST_BACKTRACE=1 cargo build
12 - RUST_BACKTRACE=1
16 - RUST_BACKTRACE=1 LLVM_CONFIG_PATH=llvm-3.8-config
11 RUST_BACKTRACE: short
19 RUST_BACKTRACE: 1
84 `RUST_BACKTRACE=1`;86 - If you want only panics to have backtraces, set `RUST_BACKTRACE=1` and
12 RUST_BACKTRACE: "1"
12 RUST_BACKTRACE: full
11 - export RUST_BACKTRACE=full
28 export RUST_BACKTRACE=1
101 export RUST_BACKTRACE=1
110 export RUST_BACKTRACE=1
9 RUST_BACKTRACE: 1
74 env::set_var("RUST_BACKTRACE", "1"); in log_panic_info()
13 RUST_BACKTRACE: 1
12 RUST_BACKTRACE: 1
329 /// variables `RUST_LIB_BACKTRACE=1` or `RUST_BACKTRACE=1` must be defined335 /// `RUST_BACKTRACE=1`;338 /// - If you want only panics to have backtraces, set `RUST_BACKTRACE=1` and
138 //! `RUST_BACKTRACE=1`;140 //! - If you want only panics to have backtraces, set `RUST_BACKTRACE=1` and
192 None => match env::var_os("RUST_BACKTRACE") { in enabled()
393 os.environ["RUST_BACKTRACE"] = "1"
354 os.environ["RUST_BACKTRACE"] = "1"
85 //! If the test fails, this will be printed (if `$RUST_BACKTRACE` is `1`):
218 note: Run with `RUST_BACKTRACE=1` for a backtrace.