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.
29284 Discussions

Unable to start debugging

cesarpradosboda
Beginner
‎05-31-2006 09:56 AM
678 Views

Hello,

I've just finished porting to EM64T. The program runs but when I want debugging I obtain the next message:

Unable to start debugging

Unable to start the program, ****.exe,

The specified file is unrecognizable or unsupported binary format.

I work in a EM64T server ( Microsoft Visual C++ .NET 69459 & Intel Visual Fortran 9.0.2945.2003 ), and I can debugger in another program that has the same Debug configuration. In the project where I cant debugging I must ignore the next library LIBC, this is the only difference with the other version.

I dont understand why now, I cant debugger.

Thank in advance

Cesar

0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎05-31-2006 01:13 PM
678 Views
You are using an unsupported combination. Visual C++.NET is an IA-32 only product and cannot debug EM64T code. You need Visual Studio 2005 for that.
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎05-31-2006 01:14 PM
678 Views
You are using an unsupported combination. Visual C++.NET does not support EM64T debugging. You can use the Intel Debugger (idb) or switch to Visual Studio 2005 and Intel Fortran 9.1.
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.