Re: User breakpoint

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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



.