1
Fork 0

Explain why we save spans for some memory types and not others

Co-authored-by: Ralf Jung <post@ralfj.de>
This commit is contained in:
Ben Kimock 2023-08-15 19:26:53 -04:00 committed by GitHub
parent 1852bb8d62
commit 63a51a6b19
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -140,7 +140,9 @@ impl MiriMemoryKind {
fn should_save_allocation_span(self) -> bool {
use self::MiriMemoryKind::*;
match self {
// Heap allocations are fine since the `Allocation` is created immediately.
Rust | Miri | C | Mmap => true,
// Everything else is unclear, let's not show potentially confusing spans.
Machine | Global | ExternStatic | Tls | WinHeap | Runtime => false,
}
}