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

Can't debug on Vista.

slsfortran
Beginner
945 Views
I use mvs2008+intel fortran 11 on Vista.

When I debug it shows that "Visual Studio cannot debug because the debug taget.....is missing". Please give me some advises. Thank you!

Note: My program runs well on Windows XP. However, all programs give the message like above in Vista.

0 Kudos
8 Replies
Steven_L_Intel1
Employee
945 Views
Is the project that is the "startup project" (shown in bold in the solution explorer) an executable project? Right click on the project and select Properties, then Debug. Is a target listed? Does the executable exist?
0 Kudos
slsfortran
Beginner
945 Views
Is the project that is the "startup project" (shown in bold in the solution explorer) an executable project? Right click on the project and select Properties, then Debug. Is a target listed? Does the executable exist?

At first, thanks, Steve Lionel.

1. There is only one project in the solution explorer, so it is default as the "startup project".

2. right click -> properties -> then, Do you mean "Configuration: Debug" or "Debugging" or "Fortran: Debugging"?

3. I can't find the listed target and executable. Where are them?


Note: My mvs is 08 professional edition.
0 Kudos
Steven_L_Intel1
Employee
945 Views
First look at Configuration Properties > Debugging > Command. It shoud say $(TargetPath). Now under Linker > General look at OutputFile. It should say $(OutDir)$(ProjectName).exe Last look at Configuration Properties > General. OutputDirectory should say $(ConfigurationName). What this all means is that it will try to run an executable whose name is the name of your project, in the folder that is the configuration name (usually Debug or Release). Do you have an EXE in that folder? Did the project build successfully?
0 Kudos
slsfortran
Beginner
945 Views
First look at Configuration Properties > Debugging > Command. It shoud say $(TargetPath). Now under Linker > General look at OutputFile. It should say $(OutDir)$(ProjectName).exe Last look at Configuration Properties > General. OutputDirectory should say $(ConfigurationName).



All the above right.


Do you have an EXE in that folder? Did the project build successfully?


No exe in the folder and itis not successfully.


0 Kudos
slsfortran
Beginner
945 Views



The error information.

0 Kudos
Steven_L_Intel1
Employee
945 Views
You can't debug because there were errors during the build. You need to fix the errors and rebuild.

You may find my recent blog entry I've Come Here For An Argument useful reading, especially the section on Sequence Association.
0 Kudos
slsfortran
Beginner
945 Views
You can't debug because there were errors during the build. You need to fix the errors and rebuild.

You may find my recent blog entry I've Come Here For An Argument useful reading, especially the section on Sequence Association.

Yeah.

But the error message is not appear in my XP system, so I was confuesed.

Another question: How do I remove the message? (I mean the message don't display on the screen)
0 Kudos
Steven_L_Intel1
Employee
945 Views
Your XP system either has an old compiler or does not have generated interface checking enabled.

I don't understand your last question. To fix the error, make sure you do not pass a scalar, such as a constant 1, to an argument expecting an array. (That's the most common reason for this message, but there are others as I explained in my blog post.)
0 Kudos
Reply