diff options
| author | David Tolnay <dtolnay@gmail.com> | 2025-05-03 09:57:20 -0700 |
|---|---|---|
| committer | David Tolnay <dtolnay@gmail.com> | 2025-05-03 10:18:50 -0700 |
| commit | 00d3fdce7cb36a8c3fa090f797bdd093665cbe93 (patch) | |
| tree | 5ad573dadb72a0e30d599f41b51aadb5d4cb17ab /tests/rustdoc/enum/enum-variant-fields-heading.rs | |
| parent | d7df5bdf2986e596aeaeec38e732711c69ebbce1 (diff) | |
| download | rust-00d3fdce7cb36a8c3fa090f797bdd093665cbe93.tar.gz rust-00d3fdce7cb36a8c3fa090f797bdd093665cbe93.zip | |
Allow linking rustc and rustdoc against the same single tracing crate
By consecutively initializing `tracing` and `rustc_log`, Rustdoc assumes
that these involve 2 different tracing crates.
I would like to be able to build rustdoc against the same tracing crate
that rustc_log is also built against. Previously this arrangement would
crash rustdoc:
thread 'main' panicked at rust/compiler/rustc_log/src/lib.rs:142:65:
called `Result::unwrap()` on an `Err` value: SetGlobalDefaultError("a global default trace dispatcher has already been set")
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: rustc_log::init_logger
4: rustc_driver_impl::init_logger
5: rustdoc::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
error: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-rustdoc&template=ice.md
note: please make sure that you have updated to the latest nightly
query stack during panic:
end of query stack
Diffstat (limited to 'tests/rustdoc/enum/enum-variant-fields-heading.rs')
0 files changed, 0 insertions, 0 deletions
