This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Why does debugging "pure virtual method called" have to be so hard?
- To: egcs at cygnus dot com
- Subject: Why does debugging "pure virtual method called" have to be so hard?
- From: John Lindal <jafl at alice dot wonderland dot caltech dot edu>
- Date: Thu, 15 Oct 1998 16:16:21 -0700
- Cc: jafl at cheshire-cat dot wonderland dot caltech dot edu
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