Re: Assertion Failed
With memory corruption, the best course of action is to use
a memory tracking tool like BoundsChecker, Pirify, or Insure++.
If OP doesn't have a license yet, I highly recommend they
obtain one. It pays off many times its cost in debugging time
saved!
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"David Lowndes" <DavidL@example.invalid> wrote in message
news:jcr9o31dthndkc3cn69l219m5rr2e8d4ov@4ax.com...
I followed your instructions but the problem occurred every time in a
diffrent place
and in different type of Vars.
It may be due to pseudo-random situations, or just timing on how you
try to recreate the problem. It's the nature of the beast
unfortunately - there's often no immediately obvious cause and effect
especially if the problem only shows up a relatively long time after
the cause.
I tought it was related to some kind of heap overiding by the .net
runtime.
what do you think?
I've no idea, but I wouldn't have thought it was that.
Ensure you compile at the highest warning level (use the static code
analyser option if you have it in your version of VS) and switch on
all the compiler debug run-time diagnostic options and see if they
find anything - after that try Purify or BoundsChecker (DevPartner
Studio or whatever it's called) and see if they can shed any further
light on the problem.
Dave