Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28847 Discussions

IFX Debugger: Watch window show only first array. All other arrays are shown undefined.

NasarAli
New Contributor I
2,161 Views

IFORT debugger showing correct dimension of all arrays defined in a routine. Whereas the IFX debugger only shows first array, and all other arrays are undefined. Also, the IFX debugger is unable to determine the correct dimensions of arrays.

 

Here is the sample code (project attached) and the IFORT and IFX watch windows.

I am using Visual Studio 2022 and IFX 2024.1.0

 

NasarAli_1-1714456819414.png

 

NasarAli_2-1714456833397.png                 NasarAli_3-1714456846625.png

 

 

 

 

0 Kudos
18 Replies
Devorah_H_Intel
Moderator
2,110 Views

Thank you for reporting this to us. I have escalated it to our debugger team and will update you on the status. 

0 Kudos
andrew_4619
Honored Contributor III
2,093 Views

I thought I had reported this also. Debugger issues like this seem to be many and are now the only reason that I cannot work with IFX. I hope that these can be resolved soon.  Another example using VS2022 and the latest compilers is shown below.

module testy
    implicit none
    contains
    subroutine bill( gbuf )
        character(*) :: gbuf
        gbuf(2:2) = 'z'
    end subroutine bill
end module testy
program struct_test
    use testy
    implicit none
    character(80) :: lemon
    lemon = 'grape'
    call bill( lemon )
end

 

 

andrew_4619_0-1714518240791.png

IFORT

andrew_4619_1-1714518326286.png

IFX

 

Devorah_H_Intel
Moderator
2,030 Views

@andrew_4619 wrote:

I thought I had reported this also. Debugger issues like this seem to be many and are now the only reason that I cannot work with IFX. I hope that these can be resolved soon.  Another example using VS2022 and the latest compilers is shown below.

module testy
    implicit none
    contains
    subroutine bill( gbuf )
        character(*) :: gbuf
        gbuf(2:2) = 'z'
    end subroutine bill
end module testy
program struct_test
    use testy
    implicit none
    character(80) :: lemon
    lemon = 'grape'
    call bill( lemon )
end

 

 

andrew_4619_0-1714518240791.png

IFORT

andrew_4619_1-1714518326286.png

IFX

 


@andrew_4619  Do you refer to your earlier report
If yes, I have checked the status of the bug report—the fix is coming in the 2024.2 Intel Fortran Compiler release. 

0 Kudos
andrew_4619
Honored Contributor III
2,049 Views

I am surprised there is not more traffic on this forum with IFX debugging problems. I would have thought just the two simple reproducers above would cause plenty of headaches from someone trying to debug with IFX. If you have some problems and/or some simple reproducers please join in! Or maybe like me people just went back to IFX, made no comment and expected fixes to just turn up at some point????

0 Kudos
NasarAli
New Contributor I
2,005 Views

Yes, it seems people either did not try IFX, or if did they switch back to IFORT because of the issues.

I did it myself, tried IFX when 2024.0 was released but then switch back to IFORT. Now I have started the migration again and found issues with debugger, power operator, AND operator and BLOCK DATA. I will be soon reporting these issues. 

0 Kudos
andrew_4619
Honored Contributor III
1,960 Views

@Devorah_H_Intel , thanks, yes that previous report does look like the same issue. I note that the example I posted here does not show the same symptom, the the previous one the var gave "undefined pointer". In the latest example it shows as len=1. Those are using different compilers levels so maybe they are the same. If it is fixed in an internal build it might be worth quickly checking the new example just in case.

 

@NasarAli  Intel are chomping through IFX bugs at a great rate  at the moment which is good and I have not seen any issues to build IFX production OK  but the concept of debugging in IFORT and releasing in IFX does not seem like a good plan so I am still using IFORT. 

Devorah_H_Intel
Moderator
1,929 Views

The results of internal testing with the upcoming 2024.2 release: 

testy-2024.2.png

 

 

Console2-2024.2.png

0 Kudos
NasarAli
New Contributor I
1,025 Views

Hi @Devorah_H_Intel 

 

I just tested this with the latest 2024.2 release and the problem is still there. The only improvement is that it detects the array size correctly now, but still, it displays only the first array values. All other arrays are shown as null.

NasarAli_0-1722263321600.png

 

 

0 Kudos
Devorah_H_Intel
Moderator
993 Views

Yes, the fix is not complete. I have escalated this again to the debug team. 

0 Kudos
Devorah_H_Intel
Moderator
970 Views

@NasarAli 
I noticed that under Locals the debugger shows the values of the second array but not under the Watch. In any case, I have got the debugger team to look at this

ifx  2024.2 expanded.png

0 Kudos
andrew_4619
Honored Contributor III
1,912 Views

Great news, I will look forward to that. Thanks

0 Kudos
NasarAli
New Contributor I
1,892 Views

that's fantastic. Thanks

0 Kudos
dajum81
New Contributor I
1,531 Views

Is there a release date for the 2024.2 update?  Can you verify that the attached works for displaying the variables.  Especially XG in both the main program and in the subroutine test.

Thanks,

Dave

0 Kudos
Devorah_H_Intel
Moderator
1,506 Views

The attached project has build errors.  

0 Kudos
dajum81
New Contributor I
1,504 Views

This one worked in other folder locations.

Dave

Devorah_H_Intel
Moderator
1,497 Views

@dajum81 wrote:

This one worked in other folder locations.

Dave


Yes, I was able to reproduce the issue with the IFX debugger. I will pass it on to debugger engineering. Thank you for submitting the new test case.

0 Kudos
francisco068
Beginner
326 Views

Hello,

I just install intel developpement tools 2024.2 with microsoft visual studio and it seems I encounter similar issues. 

When I compile with ifort the debugger show all variables, but with ifx some of them disappear 

with ifort :

ifort compilation.jpg

with ifx same breakpoint:

ifx compilation.jpg

andrew_4619
Honored Contributor III
305 Views

2024.2 is out of date 2025.0.0 was release a few days ago.

Reply