On OSX 10.8.1 (Mountain Lion) the gnu profiling tool wasn’t working.
I’ve looked it up online and there was very little documentation about the problem.
I read in a couple of places saying that gprof in fact didn’t work but I couldn’t find any final answers.
Basically what happened is that when the program was compiled with the “pg” option, the gmon.out file was not created, thus not being able to run gprof to gather profile information for a specific program.
At first I thought the problem could be related to the fact that I was running gcc 4.2.1(the one that comes by default with XCode) so I tried to compile the latest version of gcc from source to check if it solved the problem.
I compiled gcc version 4.7.1. However it didn’t fix the problem.
I even try linking the profiling lib manually, but the gmon.out file was not being created.
**I’m still trying to find why the gmon.out file wasn’t being created, if anybody knows the reason or have any suggestions please leave a comment below.
My next step will be to compile the libc from source to add some profile symbols.
I’m following these references:
A couple of resources that are not related to gprof but nevertheless very useful:
With all that being said, I needed to profile a c++ program on the mac, so I went looking for alternatives.
Luckly, I found that XCode comes with some extra tools called Instruments
A few tools included in the Instruments toolset are:
- Activity Monitor
- Time Profiler
- System Trace
- Energy Diagnotics
To get started with the Time Profiler is very simple, you first need to create a Xcode project.
Select the Profile option under Product (Command + I)
Select the Time Profiler template
Finally it will display the profile of your application
So far so good, I managed to generate profile information for my application. However, what if I wanted to get the information via the command line?
In my case I had to run the same application several times with different arguments to inspect how some functions behaved in certain situations and if they needed some optimizations.
With that in mind, running the time profiler via XCode was out of the question since I would need to manually modify the arguments and run the profiler each single time.
Instead I created a bash script to automate the runs.
Now I needed to find how to run the Instruments Time Profiler via the command line.
It wasn’t easy, there is very few documentation online and the manual has some outdated information.
Instead of [-d document] the correct is [-D document]
Anyway, to run Instruments from the command line:
instruments -t PathToTemplate -D ProfileResults YourApplication [list of arguments]
To see a list with all the available templates:
The result is a trace file that will contain the information regarding the profiling of the application.