Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29295 Discussions

Debugging With Visual Studio 2008

Groundsel
Beginner
‎10-30-2008 01:19 PM
443 Views

I am trying to debug software using the 11.0.039.beta test compiler in conjunction with Visual Studio 2008. In the project properties under General and Debugging, I try to set command line arguments, specifically the source of data for the debug executable with < datafile

I have no trouble doing this with the same compiler integrated with Visual Studio 2003. However, with VS 2008, itdoes not seem to accept my command line arguments (redirections). Has anyone managed such debugging successfully?

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎10-30-2008 02:11 PM
443 Views

Works for me. I recall that an earlier edition of VS (might have been 2003) had a problem with this in that you had to specify the full path, but that got fixed in VS2005. I just tried a test in VS2008 and it worked as I expected. Remember that it will expect the file to be in the project folder (the one with the .vfproj file), not the executable folder. This is standard VS behavior.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.