Intel Fortran debugger does not show array variables or any in QuickWatch

[JF6]

Hello,

I cannot get arrays and some variables to display in a simple Fortran console program.

I've seen similar problems posted so this seems to be an Intel problem.  I followed those approaches by today reinstalling OneAPI and adding Intel GDB and Fortran Expression Evaluator and rebooting, no change in behavior:

I'm using IFX.  Same behavior if I compile the trivial program below with ifort.

The array "a" gives "an unspecificed error has occurred", and no value is shown in Quickwatch.   Even integers are not defined in Quickwatch, they are shown in the Local window. The hover over a variable does not work either, for any type.

Thanks for any help,

John

Windows 11 / Fortran IDE 2026.0 / Intel Distribution for GDB 2025.2.0 / Fortran Expression Evaluator 2026.0.0 / MSVS 17.14.39

******************************************************************************

program console3
integer :: i, j
real :: a (2,2), b

b = 2.0
do i = 1, 2
  do j = 1, 2
    a (i,j) = real (i) * real (j)
  enddo
enddo
write (*,*) a

end program console3

[Steve_Lionel]

I can't reproduce the problem.

Steve_Lionel_0-1787683827081.png

Please show a screenshot of what you're seeing.

[Andrew_Smith]

I presume you use debug options turned on in your compile? Maybe tell us all the flags used in compile and link

[JF6]

Steve, Andrew:

I've attached a screenshot and a listing of compiler, linker and about settings:

I also notice if I put a character string in Quickwatch says it's undefined, although it will display in the locals window.

I installed Fortran Expression Evaluator and GDB based on other similar reported problems, but had no effect.

Thanks for any help, especially Steve as I've followed his helpful comments since VMS days.

John

Compiler:
/nologo /debug:full /Od /warn:interfaces /module:"x64\Debug\\" /object:"x64\Debug\\" /traceback /check:bounds /check:stack /libs:dll /threads /dbglibs /c

Linker:
/OUT:"x64\Debug\Console3.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"x64\Debug\Console3.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG /PDB:"C:\prg\Console3\x64\Debug\Console3.pdb" /SUBSYSTEM:CONSOLE /IMPLIB:"C:\prg\Console3\x64\Debug\Console3.lib"

Microsoft Visual Studio Professional 2022
Version 17.14.39 (August 2026)
VisualStudio.17.Release/17.14.39+37614.0.-august.2026-
Microsoft .NET Framework
Version 4.8.09221
Installed Version: Professional

Visual C++ 2022
ASP.NET and Web Tools 17.14.150.18679
Azure App Service Tools v3.0.0 17.14.150.18679
C# Tools 4.14.0-3.26364.8+3f38462646eca9ed0f89313d36a22e031920552d
Common Azure Tools 1.10
Cookiecutter 17.0.25079.8
GitHub Copilot 17.14.1706.11463
Intel® C++ Compiler 2026.0
Intel® DPC++ Compatibility Tool 2025.3
Intel® Fortran Compiler 2026.0
Intel® Inspector 2024 1.3.21
Intel® oneAPI DPC++ Compiler 2026.0
Intel® oneAPI Menu & Samples 10.10.392.9731
Intel® Performance Libraries 2026.0
Microsoft JVM Debugger 1.0
NuGet Package Manager 6.14.3
Python - Django support 17.0.25079.8
Python - Profiling support 17.0.25079.8
Python - VC Project Support 17.0.23055.1
Python with Pylance 17.0.25079.8
Test Adapter for Boost.Test 1.0
Test Adapter for Google Test 1.0
TypeScript Tools 17.0.40502.2001
Visual Basic Tools 4.14.0-3.26364.8+3f38462646eca9ed0f89313d36a22e031920552d
Visual F# Tools 17.14.0-beta.25230.7+c1a9d78ad4a474a716ccffb4367ed5151e3f7c9f
Visual Studio IntelliCode 2.2

[caseyhunt]

I’d check the debug build settings first. If the variables are showing correctly in the Locals window but QuickWatch says the array is undefined, it sounds like the debugger has the symbol information for some variables but isn’t resolving the array expression properly.

I’d try compiling a small test case with optimization disabled and full debug information, then put the breakpoint directly on the loop and check the array from Locals/Watch rather than hovering over it. If it still fails there, a screenshot of the Locals window with the array expanded would probably help narrow down whether this is a debugger issue or something specific to the way the array is declared.