Re: User breakpoint

The exceptions come from asserts in the code. That code
has no way of knowing how the memory got corrupted.
You should be happy with the diagnostics you do get.
Tracking a memory error way past the place it can be
reasonably detected (and from seemingly random crashes
in unrelated code) would be even harder...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Dave" <dave5398@xxxxxxxxxxxxxx> wrote in message
news:eBaYqNH0GHA.4264@xxxxxxxxxxxxxxxxxxxxxxx
I tracked the error. I had written past the end of the array because I was
not using the SafeArray functions, but posting direct to the psa->pvData.
A similar error occurs when you write past the end of an array created with
the "new" keyword eg new long[1000]. It would have been better if the
error were reported as "Attempt to write past allocated memory" instead of
the completely opaque messages you get instead (User breakpoint or Debug
error! damage at block xxx).. Can this be changed?

Dave

"Dave" <dave5398@xxxxxxxxxxxxxx> wrote in message
news:uk4otSE0GHA.4176@xxxxxxxxxxxxxxxxxxxxxxx
Anyone any idea why in debug mode you get seemingly random breaks with
the message: "User breakpoint called ...." when you never did any such
thing? In my current code I call SafeArrayDestroy(psa) on a perfectly
respectable and well defined SAFEARRAY and this triggers the break. Why?
and how can I stop this?

Dave





.

Loading