an interesting g++ new/delete bug -- only defining half the set

[Martin von Loewis]

> Any thoughts on a productive way to make the compiler see that this is
> happening, and suitably warn about it?

It seems that this should be a Checker application. Purify detects
this kind of stuff and calls it 'non-matching memory deallocation' or
the like.

With proper instrumentation, you can detect it at run time. I doubt
you can detect it at compile time reliably.

Martin