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

Update link in compiler-debugging.md 

Link didn't point to latest version of `env_logger` crate.

Add an explanation to disambiguate the RUSTC_LOG syntax.
This commit is contained in:
Olivier FAURE 2020-11-11 12:31:58 +00:00 committed by Joshua Nelson
parent 95a3cfa327
commit 4da49360a6
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/compiler-debugging.md
View File

@ -149,10 +149,10 @@ $ # Cool, now I have a backtrace for the error
These crates are used in compiler for logging: These crates are used in compiler for logging:
* [log] * [log]
* [env-logger]: check the link to see the full `RUSTC_LOG` syntax * [env-logger]
[log]: https://docs.rs/log/0.4.6/log/index.html [log]: https://docs.rs/log/0.4.6/log/index.html
[env-logger]: https://docs.rs/env_logger/0.4.3/env_logger/ [env-logger]: https://docs.rs/env_logger/0.8.1/env_logger/
The compiler has a lot of `debug!` calls, which print out logging information The compiler has a lot of `debug!` calls, which print out logging information
at many points. These are very useful to at least narrow down the location of at many points. These are very useful to at least narrow down the location of
@ -166,6 +166,10 @@ then appear in standard error.
If you are developing rustdoc, use `RUSTDOC_LOG` instead. If you are developing rustdoc, use `RUSTDOC_LOG` instead.
See the [env-logger] doc for more info on the full syntax. (Note: unlike the
compiler, the env-logger crate and its examples use the `RUST_LOG` env
variable.)
**Note that unless you use a very strict filter, the logger will emit a lot of **Note that unless you use a very strict filter, the logger will emit a lot of
output, so use the most specific module(s) you can (comma-separated if output, so use the most specific module(s) you can (comma-separated if
multiple)**. It's typically a good idea to pipe standard error to a file and multiple)**. It's typically a good idea to pipe standard error to a file and