can't debug

[phost75]

my VS Version 17.14.13 and oneAPI  version  2025.2. I found that x86 platform can't compile fortran for lacking support for win32, i can compile or run the porgram in x64, but i can't debug the program for all the variables are undefined.

[jimdempseyatthecove]

Please make a small reproducer. The exercise may be enlightening.

Where are "all the variables"? (local to procedure, module, named common, in a derived type, parameters, ...)

If variables are within a module, then prefix the variable with the module name and ::

In my case the module name was "mod_toss" (the "mod_" is not a compiler decoration, rather naming choice by me)

Also note, in any procedure, variables outside of its scope, will not be visible while within that procedure.

And, should you hit a runtime error (e.g. divide by 0), the call stack will likely show the current stack level is that of the error reporting procedure. To correct this, open the Call Stack debugger window and double click on the offending procedure level.

Jim Dempsey

[andrew_4619]

2025.2 only has IFX not Ifort. IFX does not support 32 bit builds.

[JohnNichols]

The debug problem has been written about extensively on this forum, just do a simple search.   If you use the Control Panel - programs in windows to update, it will keep all of the old copies of ONEAPI so it will run IFORT, a clean install of 2025 is well no IFORT.   CP is the simplest way.