Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
34 Views

Strange behavior in memory analysis

Hi all,

I have run a memory analysis (the widest scope memory analysis type) via Inpsector XE 2013. It includes analysing of stack acceses, to cach uninitialized arrays/variables.

Attached is a PNG figure with the results.

Note the strange behavior in Polar_HUCM.F90 module, which imply there is uninitialized memory access in line 119. However, note that line 120 is identical in terms of using the same arrays and specifically the same part of the array being controlled by "kb" loop.

Am I missing something here ? Is there a more efficient way of checking for uninitialized variables/arrays?

Thanks for all your comments,

Jacob.

 

0 Kudos
2 Replies
Highlighted
Employee
34 Views

Once an uninitialized read has been reported for a variable, the memory is marked so that subsequent reads are not reported.

My guess is that it is reporting on 'bin_mass' in line 119.  Since it was reported already, the read of that variable in line 120 will not be reported.
 

0 Kudos
Highlighted
Beginner
34 Views

Hi Mark,

Yes - your guess is reasonable.

Thanks for the information about marking the memory accesses only once.

My best,

Jacob. 

0 Kudos