This has happened twice since the update from 11.6 to 12.8, and I'm wondering why the McSvHost message was preceded on both occasions by the Visual C++ message. Since I had modified the Default Action for McSvHost process (using services.msc) to restart automatically, the main annoyance was dealing with the messages. Has anyone else encountered this?
What is the latest Visual C++? According to Add/Remove programs I have a set of VC++ programs installed running from 2005 to 2010. I'm pretty certain those two error messages are connected; it's a pity the file pathname is truncated to fit in that small window, or I might have a better idea of what's going on.
The Event Log data is no more informative than the error message displayed here, and the Help & Support Center information is totally misleading since it doesn't have anything on Visual C++. The explanation is given in http://support.microsoft.com/kb/125749 and it says it's a coding error that failed to be detected at compile time.
SUMMARY
This article discusses an issue that may occur when you are developing a program.
The C++ program fails and reports the following run-time error:
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.
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.
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.
Back to the topThere's a slightly more technical explanation in http://msdn.microsoft.com/en-us/library/aa277943(v=vs.60).aspx
C Run-Time Error R6025
Visual Studio 6.0
pure virtual function call
No object has been instantiated to handle the pure virtual function call.
This error is caused by calling a virtual function in an abstract base class through a pointer which is created by a cast to the type of the derived class, but is actually a pointer to the base class. This can occur when casting from a void*to a pointer to a class when the void* was created during the construction of the base class.
Fair enough, but what's the connection with McSvHost, and what's the trigger for the fail?
Narrowing this down .... McSvHost crashed again, but this time I was watching. It happens during a McAfee update, and it's the same software exception code (0x40000015) and location (0x634fff93) in the error messages.
How Many Badges Can You Collect?
Community Help Hub
- Find Forum FAQs
- Learn How to Earn Badges
- Ask for Help
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Join the Community
- Get helpful solutions from McAfee experts.
- Stay connected to product conversations that matter to you.
- Participate in product groups led by McAfee employees.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:
