I am trying to run my OpenSees nonlinear soil model (not in the tree now) to simulate impact loops. It goes well with first 8 loops but stops at the last loop. A message popped up, reads
The exception Breakpoint
A breakpoint has been reached (0x80000003) occurred in the application at location 0x007e1760
When I debug into it, it goes to
C:\Microsoft Visual Studio/VC98/CRT/SRC/DBGHEAP.C
and point to the line:
/* break into debugger at specific memory allocation */
if (lRequest == _crtBreakAlloc)
_CrtDbgBreak();
What happened? Why the program goes well initially but can't continue?
thanks for your input.
A breakpoint in the run
Moderators: silvia, selimgunay, Moderators
memory problem...
If you can get hold of unix (linux) machine you might want to try using valgrind, a memory debugger for x86/linux machines:
http://developer.kde.org/~sewardj/
Boris
http://developer.kde.org/~sewardj/
Boris
Re: memory problem...
Thanks for help.
It turns out release windows version won't have this problem, so I just
stick with it. The previous problem was found during test run of debug
version.
It turns out release windows version won't have this problem, so I just
stick with it. The previous problem was found during test run of debug
version.
Re: memory problem...
The fact that the release version is not crashing does not mean there's no problem! You are most likely writing some data beyond the end of an array. Theoretically, the behavior of your program is unpredictable (but it might just work!). Under Debug mode, array boundary checks will generate the exception (to help you find the problem), but under Release, no check is done, which is why your program seems to run correctly.
I highly recommend that you find what's causing the problem and fix it!
mahmoud
I highly recommend that you find what's causing the problem and fix it!
mahmoud
gangwang wrote:Thanks for help.
It turns out release windows version won't have this problem, so I just
stick with it. The previous problem was found during test run of debug
version.