paweld/fpc
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/fpc/source.git synced 2025-11-14 06:19:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

* fixed profiler section

Browse Source
This commit is contained in:
peter 1999-01-15 13:23:45 +00:00
parent f67fb1b0eb
commit 9caa7fa250
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/user.tex
View File

@ -1904,19 +1904,23 @@ You can compile your programs with profiling support. for this, you just
have to use the compiler switch \var{-pg}. The compiler wil insert the have to use the compiler switch \var{-pg}. The compiler wil insert the
necessary stuff for profiling. necessary stuff for profiling.
When you have done this, you can run your program uder the gnu profiler, When you have done this, you can run your program as you normally would run
\var{gprof}, as follows : it.
\begin{verbatim} \begin{verbatim}
gprog yourexe yourexe
\end{verbatim} \end{verbatim}
Where \file{yourexe} is the name of your executable. Where \file{yourexe} is the name of your executable.
You may want to capture the outpus of the profiler in a file, since it can When your program finishes a file called gmon.out is generated. Then you can start
be quite a lot, as follows: the profiler to see the output. You can better redirect the output to a file, becuase
it could be quite a lot:
\begin{verbatim} \begin{verbatim}
gprog yourexe >gprof.out gprof yourexe > profile.log
\end{verbatim} \end{verbatim}
Hint: you can use the --flat option to reduce the amount of output of gprof. It will
then only output the information about the timings
For more information on the \gnu profiler \var{gprof}, see its manual. For more information on the \gnu profiler \var{gprof}, see its manual.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%