Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1 View

"Stack trace terminated abnormally" due to symlink

I have encountered a strange issue with tracebackqq in combination with symlinks, which causes the stack trace to terminate abnormally.

Consider a file tracebacktest.f90:

program tracebacktest
  use ifcore, only: tracebackqq
  call tracebackqq()
end program tracebacktest

which is compiled and run as follows:

ifort -traceback tracebacktest.f90 -o tracebacktest/a.out
ln -s tracebacktest/a.out test
./test

This causes a "Stack trace terminated abnormally". Similarly, if the symlink is in the same folder, the Routine/Line/Source columns only list "Unknown":

ifort -traceback tracebacktest.f90 -o a.out
ln -s a.out test
./test

I'm guessing this is a compiler issue, but please correct me if it is due to incorrect use of symlinks. I'm using ifort version 16.0.2 on Linux .

 

0 Kudos
2 Replies
Highlighted
1 View

I can reproduce this. My

I can reproduce this. My guess is that the traceback code, which needs to read the executable file, is having trouble with the symlink. I will pass this on to the developers and let you know of any news. Issue ID is DPD200409564.

Retired 12/31/2016
0 Kudos
Highlighted
1 View

I expect this to be fixed in

I expect this to be fixed in Update 4.

Retired 12/31/2016
0 Kudos