about summary refs log tree commit diff
path: root/compiler/rustc_parse/src/lib.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-02-24 23:48:44 +0000
committerbors <bors@rust-lang.org>2023-02-24 23:48:44 +0000
commitf0bc76ac41a0a832c9ee621e31aaf1f515d3d6a5 (patch)
tree62bff777f85cb032bf69f0c858aec7332865ef34 /compiler/rustc_parse/src/lib.rs
parentc5c7d2b37780dac1092e75f12ab97dd56c30861d (diff)
parent870dd1678ecf8c8ea39d67a1147f02fca5be4a6d (diff)
downloadrust-f0bc76ac41a0a832c9ee621e31aaf1f515d3d6a5.tar.gz
rust-f0bc76ac41a0a832c9ee621e31aaf1f515d3d6a5.zip
Auto merge of #91742 - cjgillot:force-backtrace, r=estebank
Print a backtrace when query forcing fails.

The aim of this PR is to help debugging incremental compilation bugs where query forcing panics.
For instance: https://github.com/rust-lang/rust/issues/90682 https://github.com/rust-lang/rust/issues/90697 https://github.com/rust-lang/rust/issues/90715 https://github.com/rust-lang/rust/issues/90739 https://github.com/rust-lang/rust/issues/91401

These bugs happen when the dep-graph attempts to force a dep-node whose fingerprint does not correspond to an actual DefPathHash. PR https://github.com/rust-lang/rust/pull/91741 attempts to hide this bug.

I still don't know how to reproduce these bugs, so I sadly could not test this debugging device.
Diffstat (limited to 'compiler/rustc_parse/src/lib.rs')
0 files changed, 0 insertions, 0 deletions