Searched full:rust_backtrace (Results 1 – 25 of 28) sorted by relevance
12
119 if os.environ.get("RUST_BACKTRACE"):120 env["RUST_BACKTRACE"] = os.environ.get("RUST_BACKTRACE")
136 if os.environ.get("RUST_BACKTRACE"):137 env["RUST_BACKTRACE"] = os.environ.get("RUST_BACKTRACE")
4 Subject: [PATCH] Support RUST_BACKTRACE settings in test_fmt6 Setting `RUST_BACKTRACE` when running tests is useful so that the logs
66 Sometimes a backtrace may be needed. In that case, set `RUST_BACKTRACE`70 $ RUST_BACKTRACE=1 cargo build
12 - RUST_BACKTRACE=1
11 RUST_BACKTRACE: short
12 RUST_BACKTRACE: full
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: 1
19 RUST_BACKTRACE: 1
5 RUST_BACKTRACE: '1'
11 - export RUST_BACKTRACE=full
28 export RUST_BACKTRACE=1
101 export RUST_BACKTRACE=1
110 export RUST_BACKTRACE=1
78 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
9 RUST_BACKTRACE: 1
13 RUST_BACKTRACE: 1
83 env::set_var("RUST_BACKTRACE", "1"); in log_panic_info()
334 /// variables `RUST_LIB_BACKTRACE=1` or `RUST_BACKTRACE=1` must be defined340 /// `RUST_BACKTRACE=1`;343 /// - 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()
385 "RUST_BACKTRACE=1",