Tree [19a379] master v3.2.0 /
History



File Date Author Commit
doc 2012-05-28 darwin darwin [eb32b3] cleaning up for release.
src 2012-06-02 darwin darwin [19a379] minor script fixes
test 2012-06-02 darwin darwin [19a379] minor script fixes
AUTHORS 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
COPYING 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
COPYING.LIB 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
ChangeLog 2012-05-28 darwin darwin [eb32b3] cleaning up for release.
Makefile.am 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
NEWS 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
README 2012-05-28 darwin darwin [eb32b3] cleaning up for release.
TODO 2012-05-28 darwin darwin [eb32b3] cleaning up for release.
bootstrap 2012-04-25 darwin darwin [2b1fcd] initial build tools fixes
config.h.in 2012-02-02 darwin darwin [966977] initial merge: fcdump, fcmanager, convert to gi...
configure.in 2012-06-02 darwin darwin [19a379] minor script fixes

Read Me

FunctionCheck by Y.Perret (V3.2)
--------------------------------

Give feedback or bug reports at https://sourceforge.net/projects/fnccheck/



How to compile & install:
-------------------------


 1.  ./bootstrap

 2.  ./configure

 3.  ./make install



How to use the profiler:
------------------------

1.  Compile program to be profiled using gcc/g++ with the following options:

    -lfc -finstrument-functions -g

2.  Run the program to be profiled.

3.  Run fcdump on the same current directory with profiled program:

    fcdump <profiled_program>



Installed components:
---------------------

1.  libfc.so   - shared library loaded with profiled program to hook function calls

2.  fcmanager  - program to read data from the shared library buffer and writes to 'functioncheck.fc'

3.  fcdump     - program to display profiling data from 'functioncheck.fc' log.

4.  libfc.info - documentation info



For more information:
---------------------

1.  Read documentation at .\doc folder.

2.  See diferent sample test programs on .\test folder.