Why does the error message point to the wrong source line?

Les Neilson
Total Points:
5,816
Status Points:
5,316
Brown Belt
November 4, 2009 1:00 AM PST
Rate
 
#5 Reply to #4
Quoting - Dogbite

Well, since you suggested it, I have.  This is my first time w/ this debugger, and I found that the program was ending in an output routine.  Mind you, this is about 115,000 sections before is should be doing any output!  I note that when I hover over the input arguments they don't have values, instead the ominous notation "undefined address."  This seems to suggest that the program is not entering the routine through the front door -- in fact the icon in the left column is a green arrow with the advisory that this is the next statement to be executed after returning from a call to some other function.  Meanwhile the output window is showing a fp overflow at an unknown address.  (sigh)

"Heisenbugs" (ones that move the closer you look at them) are often problematic to solve.
That said the usual cause is something overwriting memory it shouldn't (array bounds exceeded), mismatched arguments (causing stack corruption) and the process is

"implicit none" in all your fortran code
compile all DEBUG configurations with optimisation off, check routine interfaces on,
run time diagnostics array/string bounds and uninitialised variables on.

These should help narrow down the cause of the problem.

HTH
Les

Intel Software Network Forums Statistics

8492 users have contributed to 31630 threads and 100777 posts to date.
In the past 24 hours, we have 27 new thread(s) 124 new posts(s), and 165 new user(s).

In the past 3 days, the most popular thread for everyone has been Implicite multithreading ??? The most posts were made to Crash when loading skeleton The post with the most views is Dear Steve, excuse me for a d

Please welcome our newest member mdward