Instrumental profiling, such as gprof, is not particularly useful if you really just don't want to know about call graphs and the number of times these functions are called. Much more useful for performance analysis is the sampling profiler, and this Apple Shark tool (part of the CHUD) is one of the best.
You really don't need to use Xcode to create a profiling application in Shark - I have command line tools created using the Makefile that I constantly profile with Shark. You can either automatically activate Shark from your code (there are several different APIs for this), or you can use the command-line tool "chudRemoteCtrl" ( man chudRemoteCtrl ), or you can simply configure the startup parameters in Shark to set the executable path, working directory , command line arguments, etc., and you leave. Make sure you create an application with -g so that Shark can display the source code rather than the disassembled object code.
Acoustic configuration for the command line tool http://www.freeimagehosting.net/uploads/386737a1fa.jpg
Paul r
source share