|
Post by brakeline on Aug 14, 2007 6:51:35 GMT
am gettin an error code sometimes "Microsoft Visual C ++ Runtime Library R6025 " any thots ps it also mentions the Vodafone modem
|
|
|
Post by Burchy on Aug 14, 2007 8:40:57 GMT
CAUSE 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.
Back to the top RESOLUTION 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.
|
|
|
Post by Burchy on Aug 14, 2007 8:49:27 GMT
Can't seem to modify that post any more. Wardourdrive - any ideas?
|
|
|
Post by wardourdrive on Aug 14, 2007 9:16:20 GMT
If you have the complete error message it would point us to the correct area to investigate.
It will point towards a .exe or .dll file usually.
|
|
|
Post by Les on Aug 14, 2007 9:34:51 GMT
CAUSE 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.
Back to the top RESOLUTION 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. Ive tried my language decoder programme on the puter, but it did not recognise a single word of the above, so I tried reading it again but it made my head hurt
|
|
|
Post by BADGER on Aug 14, 2007 10:20:34 GMT
Must be a Alien language Les. Iam from up north, and its nowt ive herd of..
|
|
|
Post by brakeline on Aug 14, 2007 19:59:17 GMT
CAUSE 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.
Back to the top RESOLUTION 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. er anybody knows wot this means nice explanation tho
|
|
|
Post by lightspeed on Aug 14, 2007 22:02:15 GMT
I'd suggest trying to track down the Vodafone folks and ask them why their modem is making illegal virtual function calls on your time???
|
|
|
Post by ZRX Gremlin on Aug 15, 2007 20:40:23 GMT
CAUSE 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.
Back to the top RESOLUTION 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. Oddly enough if you try reading that upside down it makes just as much sense. I've just Googled "Microsoft Visual C ++ Runtime Library R6025" and I'll let you know if I find an answer in English.
|
|
|
Post by BADGER on Aug 16, 2007 6:35:56 GMT
|
|
|
Post by brakeline on Aug 16, 2007 7:17:04 GMT
course you can Badge :sleep:
|
|