Skip to main content

Return to Answer

deleted 11 characters in body
Source Link
Matthieu M.
Matthieu M.
  • 296k
  • 51
  • 471
  • 746

Ok, I've found the way. The generated callgrind.out file you can convert to dot file using gprof2dotgprof2dot (yes, this tool can parse callgrind files as well). And then you can get the graph image using dot -T<type> dotfile.dot -o graphfile.<type>

Ok, I've found the way. The generated callgrind.out file you can convert to dot file using gprof2dot (yes, this tool can parse callgrind files as well). And then you can get the graph image using dot -T<type> dotfile.dot -o graphfile.<type>

Ok, I've found the way. The generated callgrind.out file you can convert to dot file using gprof2dot (yes, this tool can parse callgrind files as well). And then you can get the graph image using dot -T<type> dotfile.dot -o graphfile.<type>

Source Link
maverik
maverik
  • 5.6k
  • 4
  • 37
  • 55

Ok, I've found the way. The generated callgrind.out file you can convert to dot file using gprof2dot (yes, this tool can parse callgrind files as well). And then you can get the graph image using dot -T<type> dotfile.dot -o graphfile.<type>