explain error code 151

AShte · ‎10-12-2015

I get error code 151 when trying to allocate an array.

I have -traceback, but still don't get any further info.

In another thread, I saw 151 being associated with allocating

an array that is already allocated. Is this the meaning of this error?

Am I missing some other flags to get this diagnostics?

Many thanks

Anton

Kevin_D_Intel · ‎10-12-2015

I doubt you are missing any compiler options. I do not know what you might be lacking to not have received the complete forrtl message. In the past there was some use of NLSPATH in locating the message catalog but I'm not sure if it is today. Maybe other possibilities are the locale or LANG setting.

What version of ifort are you using?
What does the locale command report?

The List of Run-Time Error Messages is here, https://software.intel.com/en-us/node/579769, and yes "151" does correspond to: severe (151): Allocatable array is already allocated

AShte · ‎10-12-2015

Thank you.

Yes, my bad, I found my error.

Would be great if I can figure out how to get the rull rtl error message.

Although, now that I got the link will the error codes, this is not that important.

In case it matters, below is the info you asked about:

newblue4> locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
newblue4>

Kevin_D_Intel · ‎10-13-2015

Thanks for the details. This doesn't appear related to locale settings. I'll look into this further and try recreating it and then come back to you when I have some additional insight.

FortranFan · ‎10-13-2015

@Anton S.,

What further diagnostics are you looking for? Do you use "ERRMSG=" attribute in your ALLOCATE statement?

See this thread: https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/594911, message #5 with a simple code snippet that shows an ALLOCATION error 151. Have you considered error handling your ALLOCATE statements similarly?