Has anyone figured out if Intel Inspector will get tricked if memory is deallocated through a different pointer than it was originally associated with? For example if I have a array pointer that I allocate space for, and fill, then I point another array pointer to the original pointer, and deallocate the memory by the new pointer? If I try to deallocate the old pointer I get run time errors, if I don't deallocate it the Inspector reports a memory leak. Is this really a leak? Any help is appreciated.
Is it possible to get a small reproducer?
This example works fine for me (compiled on Windows with Composer XE 2013, 64 bit):
integer, pointer :: array1(:),array2(:)
do i = 1,100
array1(i) = i
array2 => array1