×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Debug in Compaq Visual Fortran ver. 6.6

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

RE: Debug in Compaq Visual Fortran ver. 6.6

Should post in Tek-Tips.  They're more geared for this type of question

TTFN



RE: Debug in Compaq Visual Fortran ver. 6.6

Hi
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 ;>)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login


Resources


Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close