Difference between revisions of "FPProfiler"
|Line 25:||Line 25:|
[[Image:Fpprofiler_flatreport.png]] [[Image:Fpprofiler_callgraph.png]] [[Image:Fpprofiler_memorychart.png]]
== Installing ==
== Installing ==
Revision as of 13:35, 18 September 2010
The Free Pascal Profiler is an effort to create an FPC native profiler, deployable on all platforms and architectures the Free Pascal compiler itself supports. It was initially developed by Darius Blaszyk.
Free Pascal Profiler consists of two tools (fpp and fppview) and some units containing the profiling code that needs to be linked in.
To compile your project, you pass the same parameters to FPP as you would to FPC. FPP then scans your source code and inserts profiling code in each begin..end block. It also ammends the uses clause to link in the fpprof unit. Once done, it compiles your project, which now includes the profiling code. After that, it restores your units to there original state.
When you run your program that contains the profiling code, it generates an xml file containing all the profiling information. FPPView reads this xml file and generates reports from it. Call counts, timing and call graphs are supported at the moment.
A graphical frontend for Lazarus exists. For now it only is able to analyse the log files, but future versions will also enable to compile the application directly with fpp and analyse the results.
You can get the latest sources from SVN here:
Alternatively Graeme Geldenhuys has created a git repository:
This repository is an unofficial one. The SVN repository is therefore advised.
Platforms / architectures
Because it is completely FPC native, it should work on all platforms and architectures that FPC supports.
Reporting bugs / feature requests
If you find a bug and would like to report it, or you have an idea to expand fpprofiler, please report the issue in mantis and drop a note on the FPC-devel mailinglist. This ensures the issue does not get forgotten. Of course, when a patch is provided, the issue is likely to be resolved much quicker. It's also highly recommended to provide a test program with the reported issue. This program will be added to the test suite to ensure no regressions will go unnoticed.