Skip to content

Commit c15e119

Browse files
PoignardAzurJoshua Nelson
authored andcommitted
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.
1 parent 0a1da4f commit c15e119

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

src/compiler-debugging.md

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

0 commit comments

Comments
 (0)