Hi Allyn, [this is a little offtopic here, as "op2calltree" is a script distributed with KCachegrind, and does not have anything to do with Valgrind]
On Tuesday 31 March 2009, Allyn Dimock wrote: > I am running oprofile collecting (samples of) callgraph, and running the > output through the op2calltree running kcachegrind on the output file. > I would not expect an accurate callgraph since I am sampling, but the > name of the converter seems to indicate that I should get something. A very old version of the callgrind tool was actually called "calltree", and "op2calltree" just meant "converter from oprofile to calltree format". At time of writing this converter, oprofile was not able to get at call relationships, so this converter just converts samples/self costs. > kcachegrind does give me a nice, cumulative (I assume) version of > opannotate in its source window. But "Callers" and "Callees" displays > are blank, and "Call Graph" just shows the node for the function that I > have selected. Yes, to be expected. > Is there a later version of op2calltree that works better? No, sorry. Actually, it is quite a bad idea to parse the human readable output of "opreport", as the format can change in subtle ways. The converter should really be rewritten to use the XML format. And this is even more true for the butterfly output of "opreport -c". Last time I checked, "opreport -c" run forever on my distribution, which seemed to be a problem with a very slow debug reader; thus, I had no motivation to rewrite the converter. However, patches always welcome ;-) Cheers, Josef ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
