traceback not working with openmpi

Craig_P_1 · ‎07-26-2016

Hi, I'm compiling a code with the intel fortran compiler 11.1.046 and openmpi 1.3.3. I'm trying to use the -traceback option to detect errors in my code, but it doesn't seem to be working when the code is compiled with mpi, only when a serial version of the code is compiled. Is traceback supposed to work with an openmpi code? Thanks!

The compiler options I'm using are:

-FR -assume byterecl -g -debug all -traceback -check all

and the link options are (not sure if I need these flags for linking, but I do it anyway):

-g -debug all -traceback -check all

The output I get with the serial version is:

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

Image PC Routine Line Source
vasp5_debug 0000000000EF1C3D Unknown Unknown Unknown
vasp5_debug 0000000000EF0745 Unknown Unknown Unknown
vasp5_debug 0000000000E9F249 Unknown Unknown Unknown
vasp5_debug 0000000000E4EF7D Unknown Unknown Unknown
vasp5_debug 0000000000E4F382 Unknown Unknown Unknown
vasp5_debug 000000000044BDE8 MAIN__ 2593 main.F
vasp5_debug 0000000000404B8C Unknown Unknown Unknown
libc.so.6 00000039C861D994 Unknown Unknown Unknown
vasp5_debug 0000000000404A99 Unknown Unknown Unknown

The output I get with the mpi version is:

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

Image PC Routine Line Source
vasp5_debug 00000000011FB9FD Unknown Unknown Unknown
vasp5_debug 00000000011FA505 Unknown Unknown Unknown
vasp5_debug 00000000011B4419 Unknown Unknown Unknown
vasp5_debug 000000000116414D Unknown Unknown Unknown
vasp5_debug 0000000001164552 Unknown Unknown Unknown
vasp5_debug 000000000048196D Unknown Unknown Unknown
vasp5_debug 0000000000439F3C Unknown Unknown Unknown
libc.so.6 00000031B441D994 Unknown Unknown Unknown
vasp5_debug 0000000000439E49 Unknown Unknown Unknown
forrtl: severe (408): fort: (7): Attempt to use pointer KINEDEN when it is not associated with a target

Image PC Routine Line Source
vasp5_debug 00000000011FB9FD Unknown Unknown Unknown
vasp5_debug 00000000011FA505 Unknown Unknown Unknown
vasp5_debug 00000000011B4419 Unknown Unknown Unknown
vasp5_debug 000000000116414D Unknown Unknown Unknown
vasp5_debug 0000000001164552 Unknown Unknown Unknown
vasp5_debug 000000000048196D Unknown Unknown Unknown
vasp5_debug 0000000000439F3C Unknown Unknown Unknown
libc.so.6 00000031B441D994 Unknown Unknown Unknown
vasp5_debug 0000000000439E49 Unknown Unknown Unknown
--------------------------------------------------------------------------
mpiexec has exited due to process rank 5 with PID 5902 on
node compute-1-21.local exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpiexec (as reported here).
--------------------------------------------------------------------------
forrtl: severe (408): fort: (7): Attempt to use pointer KINEDEN when it is not associated with a target

Image PC Routine Line Source
vasp5_debug 00000000011FB9FD Unknown Unknown Unknown
vasp5_debug 00000000011FA505 Unknown Unknown Unknown
vasp5_debug 00000000011B4419 Unknown Unknown Unknown
vasp5_debug 000000000116414D Unknown Unknown Unknown
vasp5_debug 0000000001164552 Unknown Unknown Unknown
vasp5_debug 000000000048196D Unknown Unknown Unknown
vasp5_debug 0000000000439F3C Unknown Unknown Unknown
libc.so.6 00000031B441D994 Unknown Unknown Unknown
vasp5_debug 0000000000439E49 Unknown Unknown Unknown

Craig_P_1 · ‎07-26-2016

It also doesn't work with ifort 2013.0.079

Steven_L_Intel1 · ‎07-27-2016

It may be that OpenMPI is somehow preventing the traceback code from reading the executable. You're also using a very old compiler and it's possible that we made enhancements in the intervening years that resolved this. That it works in a serial program indicates that the traceback feature itself is functioning - I'm not sure what more we can do for you here.

Craig_P_1 · ‎07-27-2016

Okay, thanks. I'll see if I can try newer versions of ifort and openmpi