Debugging an allocation problem

[alexposts]

Hi,

I am a bit new in using ifort for linux. I have to modify a code which use big arrays. The problem is when I run the program, it works but when it starts to manipulate big arrays I have this message :

forrtl: severe (174): A pointer passed to DEALLOCATE points to an array that cannot be deallocated

and some columns (Image, PC, Routine,Line and Source) appears.
I have also several lines. In the image column, there is the name of my program, and the PC column, there is a hex number which represents (I think) the instruction pointer. The over coulumns contains the "Unknown" string.

I want to know if it is possible with the idb or gdb debuggers to know which arrays are badly allocated or deallocated ? And if I need to use the values of the PC column or special compilation options (differents than -g) for a better debugging ?

Thanks

[TimP]

Adding STAT= error checking to the ALLOCATE and DEALLOCATE, and possibly some ALLOCATED() checks, ought to be a useful step. You might take into account that f90 didn't require automatic deallocation of arrays without SAVE attribute when they go out of scope. There remain cases where module variables could be deallocated automatically by most but not all f95 compilers.