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:
parent
1852bb8d62
commit
63a51a6b19
1 changed files with 2 additions and 0 deletions
|
@ -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,
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue