Question about Computers & Internet
Runtime error R6025
- pure virtual function call
This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.
Cause: The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description.
Solution: Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.
One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.
Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.
Posted on Nov 27, 2009
Tips for a great answer:
Sep 25, 2014 | Computers & Internet
Nov 14, 2012 | Computers & Internet
Sep 30, 2010 | Computers & Internet
Jun 25, 2009 | Computers & Internet
Oct 08, 2008 | Microsoft Windows XP Professional
Oct 05, 2008 | Computers & Internet
630 people viewed this question
Usually answered in minutes!