topic Re: debug problem with fortran 2025.3.0 in Intel® Fortran Compiler

debug problem with fortran 2025.3.0

phost75 — Thu, 06 Nov 2025 05:25:53 GMT

I am unable to debug in the environment of Visual Studio 2019 + Intel@Fortran Essential 2025.3.0 — all variables appear as "undefined" during debugging.

Previously, I encountered debugging issues with VS2022 + Intel Fortran 2025.2.1. After switching to VS2019, debugging finally worked—though I had to explicitly specify the module name along with the variable name when inspecting variables in modules. I assumed that version 2025.3.0 would resolve this issue, but now debugging is completely broken.

I have two questions: Is Intel Fortran 2025.2.1 still available for download? I’d like to roll back to that version, but I can no longer find the installer. When can we expect a fix for this debugging issue? Thank you very much for your assistance!

Re: debug problem with fortran 2025.3.0

andrew_4619 — Thu, 06 Nov 2025 14:24:52 GMT

Other than the usual problems 2025.3 debug works ok. Your install is broken and needs repairing or a reinstall.

Re: debug problem with fortran 2025.3.0

WangWJ — Fri, 07 Nov 2025 07:37:55 GMT

Try reinstalling the Intel Fortran Expression Evaluator plugin in Visual Studio. The 2025.2.0 version includes this plugin, but for some reason, it is not included in the 2025.3.0 version.

Re: debug problem with fortran 2025.3.0

phost75 — Fri, 07 Nov 2025 13:14:24 GMT

the fee plugin is for vs2022 only ,i can't find plugin suit for vs 2019

Re: debug problem with fortran 2025.3.0

andrew_4619 — Fri, 07 Nov 2025 13:42:18 GMT

FEE is part of the standard Fortran instal but is also available as a separate VS plugin. I think when that was initially released it had some bug fixes for the then current Fortran release. I do not think this instal adds anything unless you have an older version installed or your fee instal is broken and it is quicker to run this than the full instal.

Re: debug problem with fortran 2025.3.0

jirina — Sat, 08 Nov 2025 09:26:33 GMT

I had the same problem with debugging in Visual Studio 2022 after installing oneAPI 2025.3. I always install any new version by uninstalling the older one, restarting the computer, installing oneAPI Base Toolkit, restarting the computer, installing oneAPI HPC Toolkit, and restarting the computer.

I do not think such a way of installing oneAPI should result in a corrupted installation, especially if no other programs were running during the installation. But who knows if CrowdStrike which I cannot pause/disable is not interfering with the installation.

Anyway, downloading and installing FEE as a VS extension helped, and now I can see variables' values correctly, including module variables without specifying the module name, and I do not need to specify variables to watch in capitals, which was necessary before FEE was added as an extension.

Thank you very much for your suggestion, it saved me a lot of time.