Skip to content

Commit 369d9b9

Browse files
authored
docs: correct logging documentation accuracy in debugging.md (#12287)
Update logging instructions and references in debugging.md
1 parent 8c2ae1d commit 369d9b9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/dev/debugging.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This is a working document intended to outline some commands contributors can us
66

77
All crates use [tracing](https://docs.rs/tracing/latest/tracing/) for logging. A console formatter is installed in each binary (`cast`, `forge`, `anvil`).
88

9-
By setting `RUST_LOG=<filter>` you can get a lot more info out of Forge and Cast. For example, running Forge with `RUST_LOG=forge` will emit all logs of the `cli` crate, same for Cast.
9+
By setting `RUST_LOG=<filter>` you can get a lot more info out of Forge and Cast. For example, running Forge with `RUST_LOG=forge` will emit all logs from the `forge` package, same for Cast with `RUST_LOG=cast`.
1010

1111
The most basic valid filter is a log level, of which these are valid:
1212

@@ -16,6 +16,6 @@ The most basic valid filter is a log level, of which these are valid:
1616
- `debug`
1717
- `trace`
1818

19-
Filters are explained in detail in the [`env_logger` crate docs](https://docs.rs/env_logger).
19+
Filters are explained in detail in the [`tracing-subscriber` crate docs](https://docs.rs/tracing-subscriber).
2020

2121
You can also use the `dbg!` macro from Rust's standard library.

0 commit comments

Comments
 (0)