victor marian wrote:
When I run a .exe file (Fortran code)
the program hangs up at the end and
gives a .exe.stackdump file.
I read in the gdb guide what a stack is.
Can I use only the .exe.stackdump file to debug the
program?
I tried
gdb prog.exe.stackdump and it is not working.
Do I have to run the program again in gdb and examine
the stack?
Thank
you.
As far as I know, a cygwin .stackdump has only the function of showing
the call stack. You might be able to use it to help verify when you get
to the same program state under gdb.
