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

An error occurred while trying to open an editor in IFX Debugging

Haku
Novice
‎09-06-2024 08:51 PM
1,049 Views

I have a simple piece of code, and the debugging mode is set to Full messeage.

when debugging, I first hit the breakpoint as shown in the 5th image , after stepping into the code, the error from the 6th error appears,

"""

( Locating source for 'C:\Users\baihaodong\source\repos\test_2\test_2\test_2.f90'. (No checksum.)
Found partial match #1: C:\Users\baihaodong\source\repos\test_2\test_2\test_2.f90 (No checksum.)
The debugger will use the source at location 1.
Opening file 'C:\Users\baihaodong\source\repos\test_2\test_2\test_2.f90' in the source file editor failed. Operation not supported. Unknown error: 0x80070057.)

"""

after this point, I can step into the code, then I go to 7th image.

This error appears every time  I step into a subroutine which located in a different file.

Previously I used ifort with almost the same configuration and it works well, could anyone provide a solution to this issue?


Haku_0-1725680388537.pngHaku_1-1725680396678.pngHaku_2-1725680402699.pngHaku_3-1725680409168.png

Haku_4-1725680492369.png

Haku_5-1725680541771.png

Haku_7-1725680648083.png

 

 

Labels (2)
Labels:
0 Kudos

Link Copied

0 Replies
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.