mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo

This commit is contained in:
Camelid 2021-02-07 19:07:48 -08:00 committed by Joshua Nelson
parent b0ff83f007
commit 4f16f7cc1d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/compiler-debugging.md
View File

@ -34,7 +34,7 @@ could be useful for debugging.
When you have an ICE (panic in the compiler), you can set When you have an ICE (panic in the compiler), you can set
`RUST_BACKTRACE=1` to get the stack trace of the `panic!` like in `RUST_BACKTRACE=1` to get the stack trace of the `panic!` like in
normal Rust programs. IIRC backtraces **don't work** on MinGW, normal Rust programs. IIRC backtraces **don't work** on MinGW,
sorry. If you have trouble or the backtraces are full of `unknown`, sorry. If you have trouble or the backtraces are full of `unknown`,
you might want to find some way to use Linux, Mac, or MSVC on Windows. you might want to find some way to use Linux, Mac, or MSVC on Windows.
@ -82,7 +82,7 @@ stack backtrace:
If you want to get a backtrace to the point where the compiler emits an If you want to get a backtrace to the point where the compiler emits an
error message, you can pass the `-Z treat-err-as-bug=n`, which will make error message, you can pass the `-Z treat-err-as-bug=n`, which will make
the compiler panic on the `nth` error on `delay_span_bug.` If you leave the compiler panic on the `nth` error on `delay_span_bug`. If you leave
off `=n`, the compiler will assume `1` for `n` and thus panic on the off `=n`, the compiler will assume `1` for `n` and thus panic on the
first error it encounters. first error it encounters.