Symbols are unavailable in some Intel Fortran code.

[Ben136KBC]

Attached a folder which can be unzipped (I had it as f:\ConsoleApplication1). It contains one C++ file compiled via Visual Studio 2019, and one Fortran file compiled via Intel Fortran, all native Windows code using OBJ / PDB file format, and linked together using the Microsoft linker (code is in the root directory, exe and obj and pdb files are in the X64\Debug subdirectory). The C++ code calls into the Fortran code. Running on Windows 11, x64, native code.

It uses the C/C++ extension and then the Modern Fortran extension (https://github.com/krvajal/vscode-fortran-support). "Modern Fortran does not have a debug adapter of its own, we plug in to Microsoft's C/C++ extension Debug component. We rely on the fact that C++ debuggers understand Fortran".

The Visual Studio Code version and installed extensions is shown below.

Open the top folder in Visual Studio Code. If you put a breakpoint in the Fortran file in test, it hits it and you can local variables and NOPROP. See ConsoleApplication1.png.

However, now put a breakpoint in the larger method, see ConsoleApplicaiton3.png. Now you cant see any variables.

If you debug this using Visual Studio 2019 with Intel Fortran, you can see all the variables.

Can you please investigate? Please help!

Install the C/C++ extension, the Modern Fortran extension. Pretty much all of the symbol information gets handled by the C/C++ extension. Perhaps it just needs a few minor tweaks to handle the Fortran symbols?

PLEASE?

ConsoleApplication1.zip

[WardenGnaw]

Can you add the following to your launch.json and share the output in the Debug Console?

"logging": {
   "engineLogging": true
}

[Ben136KBC]

Here is the log file.

DebugLog.txt

Note that in some cases it shows all the local variables fine (but for the same project sometimes not, see earlier screen shot of the same breakpoint, you just see "error processing variables request"), see this screen shot, but the watch and flyby windows cant identify the variable. Seems fishy, if the local variables can find and show it, why not the watch window?

Please note the entire project is attached earlier, so you can reproduce and investigate.

[WardenGnaw]

Ah. I missed this statement.

If you debug this using Visual Studio 2019 with Intel Fortran

The Visual Studio Debugger uses Intel Fortran as an Expression Evaluator to see if they could resolve the expression.

This would be on Intel Fortran creating an EE as a Concord extension in VS Code.

See https://github.com/microsoft/ConcordExtensibilitySamples/wiki/Support-for-VS-Code-cppvsdbg-Scenarios

[Ben136KBC]

The symbols are all already inside the PDB and OBJ file, very often you see the local variables, see screen shot in the my last comment, but sometimes it just gives an error. Which tells me it so almost works as is, just a small tweak may be required somewhere. I can't see in this extension where it handles the Watch window expressions and evaluates them? The modern fortran extension pretty much just relies on the cppvsdbg extension. if I wanted to debug this, where in this extension would I put a breakpoint? (Intel will not develop an extension for Visual Studio Code.)

[WardenGnaw]

Unfortunately, cppvsdbg is not open-sourced. It is shipped with the VS Code extension to allow debugging support for MSVC.

This is up to Intel to decide if they wish to ship their EE as a Concord Extension to VS Code.

In the meantime, this scenario is only fully supported in Visual Studio with the Intel Fortran extension.

[github-actions]

This issue has been closed automatically because it's labeled as 'external'.