Hello Josef,
On Tue, Feb 16, 2010 at 3:43 PM, Josef Weidendorfer <
[email protected]> wrote:
> On Tuesday 16 February 2010, David wrote:
> > without "--collect-jumps=yes" ("valgrind --tool=callgrind" only).
> > Thank you for your reminder. I will check with the option
> > --collect-jumps=yes after this discussion.
>
> I was confused. "--collect-jumps=yes" is about jumps inside of a function,
> but you just talk about calls. So, you can ignore this option.
>
> > My assumptions are: (1) #B and #D should be the exact subroutine invoking
> > counts for that line and (2) both #A and #C should be the exact Ir
> inclusive
> > cost of this invocation instance
>
> Yes.
>
That is great.
> which could be found out in the output of
> "callgrind_annotate --auto=yes --inclusive=yes --threshold=100".
This should give the sum of the above inclusive Ir costs, as you talked
> about
> the same called function (from same function), which maps to one line of
> the
> summary list.
>
> > The order,
> > position and times of the invocation does not matter. The number before
> the
> > "=>" should be consistent for each invocation instance.
>
> What is the meaning of "consistent" here for you?
>
For example, if in a function F1(), the subroutine SR is called three times
at the beginning, the middle, and the ending, with #A, #C and #E before the
symbol "=>", respectively. These three numbers should be identical.
Furthermore, if another function F2() also call the same SR in the
execution, the number before the "=>" symbol of the invoking line in F2()
should also be that number. I call these results "consistent". At this
point, I understand the annotated source code in this way. If this is true,
I also have another quick question. If one subroutine SR is ever called by
two caller, F1() and F2(), how can I distribute Ir count across these two
functions since the Ir counts before the symbol "=>" are always the
inclusive Ir costs? Should I turn to using the calling count (ending with an
'x') to calculate the distribution percentage?
>
> > > It would be good to provide a small test program with the wrong output
> you
> > > get.
> > > Thanks!
> > >
> >
> > I will try it when I have a chance. Maybe I should try the
> --collect-jumps
> > option first.
>
> Just forget about this option :)
>
> As I said: the fastest way to get the problem solved is to file a bug
> report
> with an small test case which reproduces the problem. EMails easily get
> lost,
> especially also for other users which have the same problem.
>
> Josef
>
Currently I made one more run to reproduce this result in my system. If I
can reproduce it, I will contact the code developer to file a bug report.
Thank you so much for your great help.
David
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
