 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / Mac Programming / July 2006gprof reporting 0 seconds execution time
Just playing around with gprof and couldn't get it to produce any timing info on 10.4.7 (on PPC). It does manage to provide correct function call counts however. The same program compiled and run on Solaris shows the timing info I was expecting. Compiling with gcc -pg file.c ./a.out gprof a.out gmon.out Thanks, Dale  Signaturedstanbro@spam.o.matic.bigpond.net.au Use Shark instead of gprof to profile your program. gprof does not work well on Mac OS X 10.4. > Use Shark instead of gprof to profile your program. gprof does not work > well on Mac OS X 10.4. No good I'm afraid - i'm using it for demonstration purposes of how to use gprof, not how to profile Mac programs per se. Do you know why it doesn't work? I tried a free bsd machine the other day and had the same problems. Dale Signaturedstanbro@spam.o.matic.bigpond.net.au > Do you know why it doesn't work? I tried a free bsd machine the other > day and had the same problems. I don't know why. All I know is I've read several posts on various message boards where people had the same problem you have. Nobody ever came up with a solution, which leads me to conclude that gprof has big problems on Mac OS X 10.4. > > Do you know why it doesn't work? I tried a free bsd machine the other > > day and had the same problems. [quoted text clipped - 3 lines] > came up with a solution, which leads me to conclude that gprof has big > problems on Mac OS X 10.4. I assume that gprof measure cpu time based on who was at bat when the 100-Hz (or 1000-Hz) interrupt ticked, probably mediated by a signal into the process being monitored. It sounds like this signal isn't happening, for whatever reason. Probably a setup issue. Joe Gwinn Gprof does not interrupt the process being monitored to determine execution time. GCC introduces hooks at compile time to count how many times the PC goes into each function, and how long it stays in each. Gprof is just used to summarize and display the data. GCC profiling operates in user-space with no specific requirement in terms of kernel modules, signaling, etc. Either the function call data is properly recorded as per the hooks put in place by GCC, but then it is not properly displayed by gprof; or the time data is not properly recorded by the GCC hooks. Either way, this is a major pain for developers used to Unix systems. Shark may be nice, but when you don't know it, when you already know gprof and need to work in a console environment... It's a major compatibility issue. > > > Do you know why it doesn't work? I tried a free bsd machine the other > > > day and had the same problems. [quoted text clipped - 10 lines] > > Joe Gwinn |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.