- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page