diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-02-03 22:20:26 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-03 22:20:26 +0900 |
| commit | 333d3d624321057ead2ce06fd346c940b9ce97bd (patch) | |
| tree | 4b9c83407d39121775ba12e81fd6409a61e95ac2 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 761705ebe5093be5bcc8f431c56ed6a330ad34e7 (diff) | |
| parent | 891368f6013398c9f10fe9383f41f02476a48e24 (diff) | |
| download | rust-333d3d624321057ead2ce06fd346c940b9ce97bd.tar.gz rust-333d3d624321057ead2ce06fd346c940b9ce97bd.zip | |
Rollup merge of #93566 - Aaron1011:rustc-backtrace, r=davidtwco
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