Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
Why are you installing the beta? The oneAPI HPC toolkit (with Fortran) is released.
Link Copied
That the variable name shows as lowercase tells me that the Fortran debug integration isn't being used. Try an uninstall and reinstall of the Intel compiler.
After re-installing Intel Fortran compiler(Intel Fortran Compiler(Beta) for Windows), the same problem exists. I have installed the following files apart from Microsoft visual studio 2019 to run and debug my Fortran code from the site (https://software.intel.com/content/www/us/en/develop/articles/oneapi-standalone-components.html#fortran
I have downloaded all files from installer 'Local'.
Can you please tell me that all the files mentioned above are required to install or not to watch the value in debugging mode? And also guide me if any other files are needed to be installed from any other source to solve my purpose.
Why are you installing the beta? The oneAPI HPC toolkit (with Fortran) is released.
After installing oneAPI HPC Toolkit with openAPI Base Toolkit, my problem has resolved. Thanks!
I have the same problem. I can not get the debug watch information.
I have installed the toolkit
My visual studio version is 2019 version 16.8.4.
See the below. I create a simple program, but I cannot watch the information.
the problem is solved for now after I unstall and reinstall everything, VS, base and Hpc.
I have the same problem after I installed oneAPI. Does it really the only solution to install again everything?
I have the same issue with recently installed (upgraded from 2019) MVSC 2022, Intel Fortran compiler 2023. I also installed the Intel oneAPI HPC Toolkit with openAPI Base Toolkit. When I scroll over variables during debugging I used to see the values in MVSC 2019, now nothing is shown. Screenshot of Locals below:
Hi Rick,
same trouble here. Have you solved the problem?
thanks.
Wen
It was helpful to set the compiler optimization option as Disable.
: Solution explorer -> Fortran project -> Properties -> Fortran -> Optimization
With options like /O3, breaking points worked, but values of variables were not available for watch.
Is your call stack in the focus of the procedure with those variables?
IOW, if your procedure with those variables, called a library procedure, and that errored .AND. EPS1 and EPS2 were global variables, then you might see what you have shown.
Jim Dempsey
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.