Skip to content

Commit 0dede7a

Browse files
committed
=debug matches debug! *and higher*
1 parent 4d9a325 commit 0dede7a

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

src/compiler-debugging.md

+9-8
Original file line numberDiff line numberDiff line change
@@ -162,14 +162,15 @@ compiler is doing a particular thing.
162162
[`debug!`]: https://docs.rs/tracing/0.1/tracing/macro.debug.html
163163

164164
To see the logs, you need to set the `RUSTC_LOG` environment variable to your
165-
log filter. Your log filter can be just `debug` to get all `debug!` output, or
166-
`path::to::module` to get *all* output (not just `debug!`) from a particular
167-
module, or `path::to::module=debug` to get only `debug!` output from a
168-
particular module.
169-
170-
For example, to get the `debug!` output for a specific module, you can run the
171-
compiler with `RUSTC_LOG=path::to::module=debug rustc my-file.rs`. All `debug!`
172-
output will then appear in standard error.
165+
log filter. Your log filter can be just `debug` to get all `debug!` output and
166+
higher (e.g., it will also include `info!`), or `path::to::module` to get *all*
167+
output (which will include `trace!`) from a particular module, or
168+
`path::to::module=debug` to get `debug!` output and higher from a particular
169+
module.
170+
171+
For example, to get the `debug!` output and higher for a specific module, you
172+
can run the compiler with `RUSTC_LOG=path::to::module=debug rustc my-file.rs`.
173+
All `debug!` output will then appear in standard error.
173174

174175
Note that you can use a partial path and the filter will still work. For
175176
example, if you want to see `info!` output from only

0 commit comments

Comments
 (0)