I have to understand a big old fortran program associate with lot's of options using similar routines. I'd like to check which subroutines (or functions) are executed under different options. What I usually do with small programs which I can access source codes is put 'print' at different check points, so I can trace the procedure.
This, however, would be a real pain and inefficient way with a big program which may have hundreds of possible brances. While I am thinking about the problem I have I found about the profiling and the VTune. I downloaded an evaluation version of the VTune and have been trying to understand how it works. I can see lots of advatages which can be achieved by using profiling without finding a solution for my own problem.
My problem is so simple and can be solved if a list of calling procedures for subroutines (or functions) executed during a running process is given. VTune results with default options show call graphs with integrated called numbers, so I cannot distinguish modules of the same routine but called at different times or points during a running process. For instance, I have a module named C which is called depending on a given value for a option.
if option == a
call C <== case 1
else if option == b
call C <== case 2
call D
end if
In VTune, the total number that C has been called is given by default. How can I distinguish case 1 and 2?
It might be so simple but not easy to find the solution as a VTune novice.
I'll really appreciate if somebody let me know how to do this.
