Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

stack overflow

lklawrie
Beginner
848 Views

Did I mention I hate these kinds of problems?

stack overflow (both 10 and 11 compilers). points to a line in the code that is calling a routine. (it's not my code but a quick perusal shows allocating and later deallocating arrays, etc).

inside the Visual studio environment, both debug and release versions complete normally.

ideas on what i should be looking for?

Linda

0 Kudos
4 Replies
Steven_L_Intel1
Employee
848 Views

Probably the compiler needs to create a temporary array because it does not know that what you are passing is contiguous. Try turning on Heap Arrays.

0 Kudos
lklawrie
Beginner
848 Views

Actually, I think it is something else. This rouitne writes out for reports.. 2 of them are written fine. The last two have no content. But perusal of code -- I think I see it.

The routine has an optional argument but instead of looking at "PRESENT" for the argument, he's testing the argument for having characters (LEN_TRIM > 0). I'll change that and I think it will likely fix it.

So the compiler is complaining after it exits the routine....

Linda

0 Kudos
lklawrie
Beginner
848 Views

FYI, though that seems like a problem, that wasn't the problem. Investigating.

Linda

0 Kudos
lklawrie
Beginner
848 Views

Ah, the proverbial uninitialized variable. A little irritating that I have "Debug everything" on in the debug compile and it doesn't/didn't catch it.

0 Kudos
Reply