https://en.wikipedia.org/wiki/P-value#History

One easy slip-up with discussing p values in the context of a workflow or a decision-making process is that a process with p < 0.05 doesn't give us any bound on the actual ratio of actually good VS lucky changes. If we only consider good changes, the fraction of false positive changes is 0%; if we only consider bad changes, that fraction is 100%. Hypothesis testing is no replacement for insight or taste.

> start reading the coredump from stdin

How does that work with multi-TB mappings, as used by niche functionality like asan?

You can run jemalloc configured with 16KB pages on a 4KB page system.