Chapter 6. Questions and Answers

6.1. How do I specify which profiler generated the profile results?
6.2. What happens when I open an application with KProf?
6.3. Why is KProf slow when I open a Palm OS profile results file?
6.4. When I try opening my text results file, KProf keeps telling me that it cannot open it.

6.1.	How do I specify which profiler generated the profile results?
	When you open a file using the Open... menu command, check the appropriate profiler name in the buttons at the bottom of the File Open dialog.
6.2.	What happens when I open an application with KProf?
	KProf first looks for a file name `gmon.out` in the same directory. If the file is found, KProf assumes that the program was compiled with GNU gprof profiling turned on (option `-pg` in GCC) and calls gprof to generate the actual profile results. If the file is not found, KProf looks for another file name `fncdump.out` which is the results of execution profiling generated by Function Check. If found, KProf calls fncdump to generate the actual results file. These operations are fully automated, all you have to do is open the executable and let KProf do the work for you.
6.3.	Why is KProf slow when I open a Palm OS profile results file?
	Profile results generated by POSE (the Palm OS Emulator) require that KProf uses function name comparisons to retrieve each function's entry. This makes the parsing of such files a bit slow.
6.4.	When I try opening my text results file, KProf keeps telling me that it cannot open it.
	Make sure that the 'x' (executable) bit is not set on your file. If in doubt, do chmod -x yourfile.