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.

DEBUG issue with IFX and VS2022

bmchenrync
New Contributor I
191 Views

frustrating.

it worked for a moment months ago.

but with either the latest VS update or Fortran update, not working again.

I search and read the many posts 

  • use ALL caps, use Module::Variable
  • a workaround of set Options variable OFF for set debug symbols in external process (Native only) which now is grayed out and selected ON?!
  • etc etc

BUT

it isn't working properly!

Can Someone provide an official 'here is how you do it' and/or which versions of IFX and VS mesh so i can STOP wasting time trying things i shouldn't have to waste my time trying!

 

I simply want variables to display properly in the DEBUG Watch window and also when i click near a variable in the code, it's value shows up!!

I used to work a certain way but now has lost it's way

 

Thank you for your assistance

(attached is the versions i am using)

 

brian

 

0 Kudos
1 Solution
bmchenrync
New Contributor I
143 Views

Figured it out.

INTEL needs to post up a checklist of what works with what.

Apparently i needed to change from

Intel oneAPI Base Toolkit

to

Intel oneAPI HPC Toolkit

when moving from IFORT to IFX

my IFORT was debugging fine but IFX wasn't debugging (or at least displaying variables)

 

moving from Base to HPC finally fixed that.

 

 

View solution in original post

0 Kudos
6 Replies
bmchenrync
New Contributor I
144 Views

Figured it out.

INTEL needs to post up a checklist of what works with what.

Apparently i needed to change from

Intel oneAPI Base Toolkit

to

Intel oneAPI HPC Toolkit

when moving from IFORT to IFX

my IFORT was debugging fine but IFX wasn't debugging (or at least displaying variables)

 

moving from Base to HPC finally fixed that.

 

 

0 Kudos
MarcGrodent
New Contributor I
136 Views

Can you please explain what you mean by "moving from Base to HPC..."? As far as I know, the Fortran compilers (ifort & ifx) have always been included in the Intel oneAPI HPC Toolkit.

0 Kudos
bmchenrync
New Contributor I
125 Views

Apparently i was directed at some point to this download for 'oneAPI Base Toolkit'

https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html

 

BUT

for IFX to work, you need this one the oneAPI HPC Toolkit

(the HPC added)

https://www.intel.com/content/www/us/en/developer/tools/oneapi/hpc-toolkit-download.html

 

not sure when/how/why i was directed to download the Base instead of HPC

But debug was not functioning properly

however

once switched,

things seem to work (for now!)

 

0 Kudos
bmchenrync
New Contributor I
107 Views

FYI

I've now reverted to IFORT 64 bit because MUCH better debug

(and it's a simple change in the Program property pages, page 1, USE COMPILER i reverted to IFORT from IFX)

 

IFX still has MAJOR issues with Debug and variables and walking though code

With IFX i was routinely getting errors like

'An error occurred while trying to open an editor'

when stepping through code/routines

which if i simply stepped another step, the error went away, but why have to deal with that?

Am i a beta tester? or is the IFX ready for primetime? (it is NOT!)

With IFORT all variables in DEBUG display properly etc etc (whereas with IFX you get a lot of problems)

 

just FYI

looking forward to the next MAJOR update of IFX to fix these many issues

 

0 Kudos
andrew_4619
Honored Contributor III
80 Views

Hmm. There are some issues with IFX debug. 

1] When stepping through code the carot often jumps around a bit erratically and sometime it might appear you are on the first line of a program branch when in fact you do not enter that branch.

2] Sometimes locally used module variable get included as symbols and sometimes you need to edit to add <module>::<var>

3] sometimes derived types components  (usually allocatable) claim to be "associated"  when in fact they are and are just fine if copied to a local have good values.

 

These I think are the only IFX debugging problem that I see and I usually manage to work around them.  There were a lot more issues previously and I could not use it, but many have been now fixed. I agreed it needs more work as it reduces productivity.  I would not agree that it is unusable as I use it daily and I am not seeing some of the issues you report above.

I would be interested in the current experience of others. 

0 Kudos
bmchenrync
New Contributor I
68 Views

Just for clarification i didn't mean to imply IFX is unusable.

Just if you need to walk through some subroutines to see values of variables it is quicker to recompile in IFORT and DEBUG

Then return to IFX for compilation and deployment

and i have large projects with thousands of lines and routines

but

thanks to modern technology they recompile very fast in either IFORT or IFX

I'm just looking forward to simply working 100% in IFX and dropping IFORT

but not yet...

 

0 Kudos
Reply