Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

unexpected breakpoint

milad_shadman
Начинающий
1 440Просмотр.
hi,

i am debugging a project. while debugging, i have blocked with this error:" 'file name' has triggered a breakpoint". this error is marked with a green sign, please see the attached file. also when i press the "step into" button this message is appeared:"There is no source code available for the current location".
please provide me with your advice.

Milad.
0 баллов
1 Решение
bmchenry
Новый участник II
1 440Просмотр.

fwiw my two bits...
ModifiedFAST.exe is the "file name" and that is the name of the EXE of your project?? so no problem there
The error seems to point to a variable on the calling arguments of TwrLoading.
do you have a break on value change or some other breakpoint related to one of the variable arguments in passed to/from TwrLoading?
Check you breakpoint list.
Isthe TwrLoading subroutine source avail?
I sometimes encounter these types of errors when jumping between debug/release and/or copying files and encounter a routine(for you it'd be TwrLoading) which might becompiled in Release and/or w/o debug information?

Просмотреть решение в исходном сообщении

5 Ответы
bmchenry
Новый участник II
1 441Просмотр.

fwiw my two bits...
ModifiedFAST.exe is the "file name" and that is the name of the EXE of your project?? so no problem there
The error seems to point to a variable on the calling arguments of TwrLoading.
do you have a break on value change or some other breakpoint related to one of the variable arguments in passed to/from TwrLoading?
Check you breakpoint list.
Isthe TwrLoading subroutine source avail?
I sometimes encounter these types of errors when jumping between debug/release and/or copying files and encounter a routine(for you it'd be TwrLoading) which might becompiled in Release and/or w/o debug information?

jimdempseyatthecove
Почетный участник III
1 440Просмотр.
On VS 2005 I had a similar problem. The only way I found to fix this was to remove all break points. Onyour VSDebug | Breakpoints you will find a button with a big red X that removes all break points. Click on this, then exit VS, restart VS, then reset your break points. This is one option.

A second potential problem is where the code gets erroneously modified to what looks like a break point. In your screenshot your message stated ...break at line nnnn in ....
Using your Debug | Breakpoints look to see if you have a breakpoint placed there. Note, I did not notice the red circle on the left frame of the text window (indicating break point). When code gets modified it is typically when you store through a wayward pointer (or the debugger is confused as described in first paragraph of this message).

Jim Dempsey
milad_shadman
Начинающий
1 440Просмотр.
bmchenry,

many thanks for your helpful advice.

Milad.
milad_shadman
Начинающий
1 440Просмотр.

bmchenry,

many thanks for your helpful advice.

milad.

milad_shadman
Начинающий
1 440Просмотр.
dear jim,

thanks for your comment,
i have checked the variables , and in this case, the message was related to variable arrangement.

Milad.
Ответить