A breakpoint in the run

For developers writing C++, Fortran, Java, code who have questions or comments to make.

Moderators: silvia, selimgunay, Moderators

Post Reply
gangwang

A breakpoint in the run

Post by gangwang »

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.
fmk
Site Admin
Posts: 5884
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk »

you probably have a memory problem .. check the pointers and arrays in your code .. somewhere you are accessing memory that does not belong to you.
Boris Jeremic

memory problem...

Post by Boris Jeremic »

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
gangwang

Re: memory problem...

Post by gangwang »

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.
hachem
Posts: 7
Joined: Mon Jan 24, 2005 4:29 pm
Location: Degenkolb

Re: memory problem...

Post by hachem »

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
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.
Post Reply