TL;DR: Catching heap corruptions of native heaps is not trivial. Therefore, catching heap corruptions of the C/C++ runtime’s heap is also not trivial.
Heap corruptions are infamously nasty. A few reasons:
- At times, they might not cause any visible errors at all, making them hard to detect
- Even if they cause an error, it usually surfaces long after the actual corruption, making them hard to pinpoint
- Memory that gets corrupted usually has nothing to do with the actual culprit
- Heap allocations of programs with a GUI are usually not fully deterministic, making a heap corruption potentially hard to reproduce
On Windows, the system can detect a subset of heap corruptions. As with most errors on Windows, this is signaled with an SEH exception. Catching this exception, however, needs some workarounds. But before we get to that, we need to take a look at the architectural relationship between the C/C++ runtime’s heap and native heaps.