From my search on Google on this topic, I am aware that the most common error associated with this error message to be writing to memory outside the dynamic memory bounds. However, as I traced back to the variable responsible for this assertion error, I have a lot of problems finding code segments that is indexing outside the array's bounds. Would there be other problems associated with this error that I'm not aware of? Thanks.
Either memory corruption (writing outside bounds) or passing in an invalid pointer can also be a cause. Use the debugger with data breakpoints to monitor the address in question to see if you can't catch the culprit.
Originally Posted by Adak
And it isn't necessarily true that the block which generates the assertion is the block which was overflowed -- it could have been an adjacent block, or in the case of a truly monstrous overflow, a block far from the block where the error was reported.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
Do you happen to have an example of what is a truly monstrous overflow? At this point, I still have no idea of exactly which block is causing the overflow. What kind of CRT debug tools from Visual Studio is available for me to use for finding this out?
