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

Unable to set breakpoints

jct_office
Beginner
1,119 Views
Sometimes,I will create a workspaceto debug a large Fortran application. I will create the workspace, add all of the various subroutines i need, andbuild the executable. Then I will attempt to set breakpoints. Initially, the breakpoints will beappear to be set. But whenI startthedebugger,Iimmediately get the error message, "One or more breakpoints cannot be set and have been disabled. Execution will stop at the beginning of the program"
In the message window, I get something like, "D:USERSDebug_testReleaseDebug_test.exe', no matching symbolic information found."
Further, any further attempt to set a breakpoint fails.
So, what am i doing wrong. Any help will be appreciated.
Jim
0 Kudos
8 Replies
gregscvf
Beginner
1,119 Views
Jim,
I get this whendebugging a CVF project, and whenI have an opened source file that is not part of the active projectset with a breakpoint. Only breakpoints in files in the active project are permitted.
Just clear this dialog box, and it should continue properly through your active project, stopping at anyvalidbreakpoints.
Greg
0 Kudos
jct_office
Beginner
1,119 Views
Thanks for the reply.
My problem seems to be much deeper. I am only setting breakpoints in subroutines included inthe active project. Further, clearing the dialog box does not seem to work; once ireceive the first error (which happens immediately), all breakpoints are "disabled," and no further breakpoints can be set.
Is there some "setting" i am missing or i have somehow erroneously changed?.
Jim
0 Kudos
Steven_L_Intel1
Employee
1,119 Views
jct_office, the message you are seeing indicates that your application is not being built with debug information. Are you using a Debug configuration? Is this CVF or Intel Visual Fortran?
0 Kudos
Steven_L_Intel1
Employee
1,119 Views
Jim,
You are trying to debug an executable built in a Release configuration. Switch to a Debug configuration.
0 Kudos
tmcole
Beginner
1,119 Views
This happens to me also and is not a result of compiling in the release configuration or setting breakpoints in a file that is not in the workspace (although I have done both of those:smileysad:.
Stop debugging and then immediately try debugging again. This always solves the problem for me.
0 Kudos
jct_office
Beginner
1,119 Views
So, how do i keep out of "release" mode and stay in "Debug" mode? I seem to have version that doesnt want to stay in debug mode.
I created a new project -- a Fortran console application, with the option of creating a new workspace. Before doing anything or adding anything to the project, i first clicked Project then Settings, then in the "settingsfor" box, I selected Win32-debug. Then clickedOK.
So far so good.
I then repeated the process. I clicked Project then Settings. Lo and behold, the"settings for" boxed showed Win-32 Release. Intermediate andOutput files show "Release"
So why is it that when i tell CVF that I want a Win32-debug, it refuses to accept my directive and give me Win32-Release.
What is going on?
BTW, why would i ever not want the debugging capabilities.
0 Kudos
Steven_L_Intel1
Employee
1,119 Views
I once had a similar problem where a CVF project would not provide a Debug configuration. I don't know what caused it and just created a new project - all was fine then. This aspect of the system is controlled by the Microsoft code.
0 Kudos
jparsly
New Contributor I
1,119 Views
"why would I not want the debugging capabilities"?
Generally, I only turn them off for programs that take a long time to run,
and then only when I'm pretty sure I've found most of the bugs.
Some of the debugging features, for example array bounds checking,
can really slow a program down.
0 Kudos
Reply