Quantcast
Channel: Intel® Fortran Compiler for Linux* and macOS*
Viewing all articles
Browse latest Browse all 2583

Back trace not produced by -traceback

$
0
0

Hello,

I have noticed this problem before with ifort, but never had a solution. Basically, I have a fairly large (modern) fortran code, which is crashing. So in order to diagnose what's causing the crash, I compiled it with the command line

ifort -fPIC -fp-model strict -fomit-frame-pointer -m64 -warn align -r8 -openmp -O2 -g -traceback -check bounds -check format -check pointers -check stack -check uninit -fpe0 -ftrapuv -fp-stack-check -gen-interfaces -warn interfaces

i.e., I put in all check and debug flags I knew. This compiled executable does give me a slightly more informative message on a crash:

forrtl: severe (408): fort: (7): Attempt to use pointer LRATE when it is not associated with a target

but it still doesn't give me a backtrace. The entity 'Lrate' occurs at many places in my code, so without a back trace it's kind of hard to figure out where the code is crashing. Is there anything else I can do to produce a backtrace?

Thanks,

Sourish


Viewing all articles
Browse latest Browse all 2583

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>