Why does debugging "pure virtual method called" have to be so hard?

[John Lindal]

Why does debugging "pure virtual method called" have to be so hard?  The
code generated by the compiler doesn't print out anything about where the
problem occurred and doesn't even dump core so one can examine the stack
trace in a debugger!

Surely it should be easy to get the compiler to generate code to dump core
when a pure virtual method is called?

John