Debug in Compaq Visual Fortran ver. 6.6
Debug in Compaq Visual Fortran ver. 6.6
(OP)
Hello,
(Silly question?)
I am using Compaq Visual Fortran ver. 6.6.
When I am in the debug mode, and the program crashes I get the assembler page with indication of the line where the program stopped.
When I go to the source code, there is no indication on where the last line was executed.
Also the since the program stopped, I have no information about the values of the various variables.
I guess I am missing something in the debugging process.
(Some link or compilations switches?)
Please advise. How am I supposed to find the bug if I do not have this information?
Regards
Tuli
(Silly question?)
I am using Compaq Visual Fortran ver. 6.6.
When I am in the debug mode, and the program crashes I get the assembler page with indication of the line where the program stopped.
When I go to the source code, there is no indication on where the last line was executed.
Also the since the program stopped, I have no information about the values of the various variables.
I guess I am missing something in the debugging process.
(Some link or compilations switches?)
Please advise. How am I supposed to find the bug if I do not have this information?
Regards
Tuli
Talk To Other Members
RE: Debug in Compaq Visual Fortran ver. 6.6
TTFN
RE: Debug in Compaq Visual Fortran ver. 6.6
http://groups.google.com/group/comp.lang.fortran
RE: Debug in Compaq Visual Fortran ver. 6.6
RE: Debug in Compaq Visual Fortran ver. 6.6
I assume you are debugging a *.exe?
If so then you should look at the messages returned in the command line window.
On the first line you will see the reference to the cause of the problem ...
examples : division by zero ...
: square root of negative number....
: etc, etc
There will also be an error code reference number. Look this up in the Compaq Help File. It may give you a clue.
Underneath the error notification you will find a list of the last run subroutines. At least you can find the routine in which the error occured, although the instigating cause may be in preceding routines.
Of course if your program is one long listing, and not split into discrete routines or functions, this may not be of much help.
You could also scroll through the assembler listing and you may find in bold type the last run code line of your program
Either way now begins the painful task of finding that error, step, by step, by step through the program ;>)