Author Topic: The call graph  (Read 3193 times)

Offline OzzyR21

  • Single posting newcomer
  • *
  • Posts: 7
The call graph
« on: November 21, 2017, 05:59:31 pm »
How (and where) do I get the call graph in code::blocks (if possible).
I mean the graph that shows how much time was spent in each function and its children

Thank you.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7591
    • My Best Post
Re: The call graph
« Reply #1 on: November 21, 2017, 06:12:37 pm »
If I recall correctly the profiler plugin; I have not used it before.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: The call graph
« Reply #2 on: November 21, 2017, 10:51:33 pm »
What operating system are you using?

Offline OzzyR21

  • Single posting newcomer
  • *
  • Posts: 7
Re: The call graph
« Reply #3 on: November 22, 2017, 10:11:05 am »
[SOLVED]

Thank you both guyzz.I am using CentOS 7.
It is profiler plugin indeed but I had to tick those:
Settings->Compiler->Compiler Flags ->Debugging->Produce Debugging symbols [-g]
Settings->Compiler->Compiler Flags ->Profiling->Profile code when executed [-pg]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: The call graph
« Reply #4 on: November 22, 2017, 08:18:29 pm »
OzzyR21: if you're going to use gprof it is best to read about its limitations. Generally these days perf is considered better profiler and the one to use when you need to measure performance. I'm using it in combination with flame graphs.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]