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

Intel Parallel Studio XE 2016 composite type variables not view able in debug

tiho
Débutant
1 786 Visites

I have a problem viewing composite type variables such of this type

A%B%pointer

Universally I get in debug "Undefined address", when they are defined and the computation works fine - but the debug windows claim it is undefined.

In contrast A%pointer is ok.

Any hints on how to overcome this problem? 

 

0 Compliments
8 Réponses
tiho
Débutant
1 786 Visites

Any comments?

0 Compliments
Lorri_M_Intel
Employé
1 786 Visites

It's hard to comment without knowing what the variable declarations look like.

               --Lorri

0 Compliments
tiho
Débutant
1 786 Visites

Any declaration. Here is a simple code

type t1 
integer, pointer :: c(:)
end type
type t2 
type(t1) :: b
end type    
type (t2) :: a
type (t1) :: b
ALLOCATE(a%b%c(1),b%c(1))    
a%b%c(1)=1
b%c(1)=1

Now if you put a%b%c in QuckWatch it says "Undefined address". This was not a problem in the earlier versions. In contrast if you put b%c in QuckWatch you get no problems,

 

0 Compliments
Steven_L_Intel1
Employé
1 786 Visites

I am not seeing this behavior with the 16.0.0 compiler and VS2013.

Capture.PNG

0 Compliments
mecej4
Contributeur émérite III
1 786 Visites

Tiho, in #4, where was the line pointer (yellow arrow) when you tried to watch the two variables? If on the line containing ALLOCATE, the pointers have not yet been defined, so what you saw ("undefined") is what you should expect.

0 Compliments
tiho
Débutant
1 786 Visites

Here is what I get. 

0 Compliments
Steven_L_Intel1
Employé
1 786 Visites

Please attach a ZIP of your project that shows the problem after a build in the 2016 version.

0 Compliments
tiho
Débutant
1 786 Visites

I figured out the problem. The project contained and old *.sln file. I delete that file and on compile a new file is created and after that the is no more problems. I am attaching the example anyway if you want to investigate it. It would be nice if the file is deleted automatically when the project is updated from VS10 to VS13. 

0 Compliments
Répondre