I'm getting intermittent R6025 (pure virtual function call) errors.
I've followed the instructions given by microsoft and added
implementations for all abstract functions and included a DebugBreak()
statement. However, I continue to get the errors. My code makes use of
DX9, but no other libraries. I've checked for memory leaks with a
couple of different tools, but after patching up a few, the problem
remained. So, the question is, what is giving me R6025? My
DebugBreak() statements never get hit and I find it unlikely that my
standard use of the DirectX library would throw these errors. All I
can think of at this point is that it's a memory/stack corruption.
Since it's intermittent, I can't place any breakpoints locate the
problem. I've tried to look for memory corruption using Software
Verify's Memory Validator, but when I try to run it with the tool, my
app crashes. Any ideas?

Re: Could memory corruption cause R6025? by kkennedy1008

kkennedy1008
Wed Nov 26 13:15:49 CST 2003

Please, someone help me. Anybody? Ideas?

Re: Could memory corruption cause R6025? by CheckAbdoul

CheckAbdoul
Wed Nov 26 13:18:22 CST 2003

See if the following KB article helps you

PRB: Cause of the R6025 Run-Time Error
http://support.microsoft.com/?id=125749

--
Cheers
Check Abdoul [VC++ MVP]
-----------------------------------

"Kevin Kennedy" <kkennedy1008@hotmail.com> wrote in message
news:78b37dd3.0311261115.277d330e@posting.google.com...
> Please, someone help me. Anybody? Ideas?



Re: Could memory corruption cause R6025? by kkennedy1008

kkennedy1008
Mon Dec 01 17:05:34 CST 2003

> See if the following KB article helps you
>
> PRB: Cause of the R6025 Run-Time Error
> http://support.microsoft.com/?id=125749

Nope. In my first post I state that none of my DebugBreak statements
get hit. These are the DebugBreak statements I set up after reading
that KB article. Again, there are absolutely no abstract functions as
I've stubbed them out in an attempt to solve this problem.