- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I recently migrated from Visual Studio 2019 Community to Visual Studio 2026 Professional and am now compiling with Intel® Fortran Compiler (IFX) 2026.0.0.
The code runs correctly, but I have a debugger issue.
Environment
- Visual Studio 2026 Professional (18.7.3)
- Intel Fortran Compiler 2026.0.0 (IFX)
- x64 Debug configuration
- Windows 11
Problem
In Visual Studio 2019 I could inspect array variables in the debugger and see all elements.
With IFX 2026, some arrays cannot be displayed in either the Watch or Locals windows.
Example:
IMPLICIT NONE
INTEGER :: NSIMS,NREM_WELLS
...
CELL = REM_WELL_CELL(SIM,I)
END SUBROUTINE
When stopped at a breakpoint:
- Scalars are displayed correctly:
RATE
SIM
- However:
REM_WELL_CELL
REM_WELL_RATE
Additional tests
I created a local fixed-size array:
so the debugger appears to know the array dimensions, but not the contents.
Question
Is this a known IFX 2026 debugger limitation/bug related to:
- adjustable arrays with runtime bounds?
- local automatic arrays?
- Visual Studio 2026 integration?
Has anyone found a workaround that allows array contents to be inspected in the debugger?
Thanks.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A few people have hit this specifically with adjustable or automatic arrays especially in x64 Debug with IFX 2026.
Workarounds that usually help:
- Try compiling with -Od -g plus disabling optimization completely (IFX sometimes still “partially optimizes” array storage).
Temporarily convert to explicit-shape allocatable arrays:
INTEGER, ALLOCATABLE :: REM_WELL_CELL(:,:)
- Or copy into a fixed-size debug buffer (what you already tried, but ensure it’s not optimized away, use VOLATILE on the source dest).
- In some cases, switching debug format to /debug:full improves watch evaluation.
Also worth noting: VS Watch window often fails with IFX unless the array has fully resolvable bounds at compile time, so this may be more of a debug info + VS natvis gap than your code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This might be due to a problem with the Fortran Expression Evaluator. Check under the Extensions tab and see if this is extension installed. You may need to Uninstall then re-install. This resulted in much better resolution of variables for me and resolved many of the error messages you're seeing.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page