Re: Bug in Visual Studio 2005?

Yes, Debug.Assert hit is the most typical case when you will see that error message.
Stepping out of Debug.Assert into your code should help.

Oleg

Thanks. I've seen this happen when a Debug.Assert() fails and I then click
the button to debug it.

"Oleg Starodumov" wrote:


It probably means that the current thread is executing code in some other module
(not yours), whose code is optimized. Often you can solve it by doing Debug | Step Out
until your own code (non-optimized) is reached. Then funceval should start
working.

If it does not help, you can post the call stack of the current thread here.

--
Oleg
[VC++ MVP http://www.debuginfo.com/]





.

Loading