Share

FunctionCheck

File Release Notes and Changelog

Release Name: 1.3.3 (pre-1.4)

Notes:
Memory management changes.

Changes: Changes from 1.3.2 to 1.3.3: * changed the exit process from fnccheck. If FNCCHK_DESTRUCTOR is set, profile file is dumped, but all data are keeped in memory. If functions call occur after (a C++ destructor), new information will be added to existing data, and the file will be dumped again. This is usefull if your destructors use 'free', because these pointers will not appear as unfreed blocks. WARNING: as a file is dumped at EACH exit from a destructor, corresponding times in the profile will not be exact anymore! Please use this option only if your want to track memory leaks, and not in "execution" profiling. * changed the memory file. No more '= End' to indicate the end of file. This is due to the changes for destructor management. * updated some parts of the doc, and the --help. * changed the way call-stack is stored in memory profile files. Now real call-site is stored, allowed to obtain the file and line numbers when displaying stack in memory leaks. Added a '(?)' at the beginning of functions in the call-stack that are not sure (it can be a call from the system, for example, but 'BFD' lib or 'nm'/'addr2line' always return a valid function name in these cases (in general the end of main())). * changed 'README.txt' into 'README' and 'CHANGES.txt' into 'ChangeLog'. * added the 'Makefile.am' and 'configure.in' for the archive (Petter Reinholdtsen). * added option '-cumul', which adds a column "cumul" to the flat profile. In this column, the cumulated local time is displayed (in percentage). Warning: using '-cumul' dont set the '-sort 1' which indicate to sort functions by local time. The cumul dont have many sense if not displayed with this sort. * added FNCCHK_QUIET variable. If set, indicates to 'fnccheck' to not display the starting message and the profile state.