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

Programm crash : how to see the function stack

tomtomms
Beginner
352 Views
Hi all,

I am right now tryng to port a fortran application from the *nix word to WS2008 x64, so I use the following tools :

Visual Studio 2008
Intel Visual Fortran 10.0.66
Sub System for Unix Application, in order to use the existing makefile

Under KSH (with SUA), I compile the source with :

ifort.exe and no special option except /debug:full

Under KSH (with SUA), then I link with wcc :

wcc -Y /VERBOSE:lib -Y /NODEFAULTLIB:msvcrt -oMYEXE.exe -L $(WSLIB) -L $(IFORTLIB) $(MPILIB)/*.lib $(HDF5LIB) $(METIS)/util.o $(METIS)/libmetis.a $(SZLIB) $(ZLIB)


Then, under a std command windows, I launch the appli :

.... read files ...

***** Total volume of the mesh, smallest cell volume :


1.184216589956522E-004 1.979724363805401E-009





WARNING CFM model:

for the moment, theta_F = 0 and thick = 1

forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source

AVBP_V6.0.ifp-sua 00000001402E3422 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 000000014021A161 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 000000014021C08E Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 00000001400362C0 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 0000000140046C9D Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 00000001400534E6 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 0000000140028AA4 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 000000014005CAB2 Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 000000014003DB3B Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 00000001403C370C Unknown Unknown Unknown
AVBP_V6.0.ifp-sua 000000014037C02F Unknown Unknown Unknown
kernel32.dll 00000000774D495D Unknown Unknown Unknown
ntdll.dll 00000000776D8791 Unknown Unknown Unknown

How could I get the full stack in order to know when the app crash ?

Best regards, Tom
0 Kudos
2 Replies
TimP
Honored Contributor III
352 Views
You would want at least to enable traceback in your final link. The debug option should have taken care of it for the ifort .obj files. I'm not familiar with this wcc command.
0 Kudos
Steven_L_Intel1
Employee
352 Views
/debug does not affect traceback. Add /traceback to the Fortran compiles and /incremental:no to the link.
0 Kudos
Reply