about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorAaron Hill <aa1ronham@gmail.com>2022-02-01 19:27:16 -0500
committerAaron Hill <aa1ronham@gmail.com>2022-02-01 22:44:22 -0500
commit891368f6013398c9f10fe9383f41f02476a48e24 (patch)
tree5cb7bfbbea9d4315c450983addecbea0ddfa44d7 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent1ea4851715893ee3f365a8ef09d47165e9a7864f (diff)
downloadrust-891368f6013398c9f10fe9383f41f02476a48e24.tar.gz
rust-891368f6013398c9f10fe9383f41f02476a48e24.zip
Make rustc use `RUST_BACKTRACE=full` by default
Compiler panics should be rare - when they do occur, we want the report
filed by the user to contain as much information as possible. This is
especially important when the panic is due to an incremental compilation
bug, since we may not have enough information to reproduce it.

This PR sets `RUST_BACKTRACE=full` inside `rustc` if the user has not
explicitly set `RUST_BACKTRACE`. This is more verbose than
`RUST_BACKTRACE=1`, but this may make it easier to debug incremental
compilation issues. Users who find this too verbose can still manually
set `RUST_BACKTRACE` before invoking the compiler.

This only affects `rustc` (and any tool using `rustc_driver::install_ice_hook`).
It does *not* affect any user crates or the standard library -
backtraces will continue to be off by default in any application
*compiled* by rustc.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions