Hi.
I'm writting tests for my application.
When running one of the tests, I get the error at the bottom.
It's weird because, the tests finish succesfully (with no error), but I get this message at the end. It's also weird because I don't get this error if I debug the tests (only if I run without debugging).
I know the line that causes the error (because if I comment it out, I don't get the error message anymore). The line is a call to a member function of a class I'm testing. However, this member function is called a lot of times in my application and I never got this error.
Can anyone explain that?
Thanks.
error here
---------------------------
Microsoft Visual C++ Debug Library
---------------------------
Debug Assertion Failed!
That usually happens in my experience when I overrun array bounds, write more data to a location in memory than I've actually allocated, or something to that effect.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
I'm writting tests for my application.
When running one of the tests, I get the error at the bottom.
It's weird because, the tests finish succesfully (with no error), but I get this message at the end. It's also weird because I don't get this error if I debug the tests (only if I run without debugging).
I know the line that causes the error (because if I comment it out, I don't get the error message anymore). The line is a call to a member function of a class I'm testing. However, this member function is called a lot of times in my application and I never got this error.
Can anyone explain that?
Thanks.
error here
---------------------------
Microsoft Visual C++ Debug Library
---------------------------
Debug Assertion Failed!
Program: d:\Leandro\Grafos\Projeto\Gtad\Test\Debug\Test.exe
File: dbgheap.c
Line: 1132
Expression: _CrtIsValidHeapPointer(pUserData)
For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.
(Press Retry to debug the application)
---------------------------
Anular Repetir Ignorar
---------------------------
That usually happens in my experience when I overrun array bounds, write more data to a location in memory than I've actually allocated, or something to that effect.
Thanks, that's pretty much it.