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
Beginner
1,399 Views

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 Kudos
8 Replies
tiho
Beginner
1,399 Views

Any comments?

0 Kudos
Lorri_M_Intel
Employee
1,399 Views

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

               --Lorri

0 Kudos
tiho
Beginner
1,399 Views

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 Kudos
Steven_L_Intel1
Employee
1,399 Views

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

Capture.PNG

0 Kudos
mecej4
Honored Contributor III
1,399 Views

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 Kudos
tiho
Beginner
1,399 Views

Here is what I get. 

(Virus scan in progress ...)
(Virus scan in progress ...)
0 Kudos
Steven_L_Intel1
Employee
1,399 Views

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

0 Kudos
tiho
Beginner
1,399 Views

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. 

(Virus scan in progress ...)
0 Kudos
Reply