22################################################################################
33
44Program : log-malloc2 (library)
5- Version : 0.3 .0
5+ Version : 0.4 .0
66Purpose : Malloc logging library with backtrace and byte-exact memory
77 tracking.
88License : GNU GPL v3 (see file COPYING)
99 GNU LGPL v3 (see file COPYING-LGPL)
10- Author : Samuel Behan <_samuel_._behan_(at)_dob_._sk> (c) 2011-2014
10+ Author : Samuel Behan <_samuel_._behan_(at)_dob_._sk> (c) 2011-2015
1111Web : http://devel.dob.sk/log-malloc2
1212 http://blog.dob.sk/category/devel/log-malloc2 (howto, tutorial)
1313
@@ -36,7 +36,7 @@ Web : http://devel.dob.sk/log-malloc2
3636------------
3737
3838 * logging to file descriptor 1022 (if opened)
39- * call stack backtrace (using GNU backtrace() if available )
39+ * call stack backtrace (via GNU backtrace() or libunwind )
4040 * requested memory tracking (byte-exact)
4141 * allocated memory tracking (byte-exact - using malloc_usable_size())
4242 * process memory status tracking (from /proc/self/statm)
@@ -82,8 +82,8 @@ Web : http://devel.dob.sk/log-malloc2
8282 * log-malloc-trackusage
8383 Script to track program memory usage over time.
8484
85- This scripts can be also used as perl packages, because they export functions
86- to parse and analyse trace file or convert backtraces.
85+ These scripts can be also used as perl packages, because they export functions
86+ to parse and analyse trace file or convert backtraces (modulino concept) .
8787
8888
8989---------
@@ -150,7 +150,7 @@ Web : http://devel.dob.sk/log-malloc2
150150 Pre-initializes backtrace() function, to avoid later memory alocations.
151151 Use of this function is optional.
152152
153- ssize_t log_malloc_backtrace(int fd)
153+ ssize_t log_malloc_backtrace(int fd)
154154
155155 Generate current backtrace including process memory map (/proc/self/maps) to
156156 make backtrace symbol conversion easier. Generated output can be directly
@@ -162,8 +162,9 @@ Web : http://devel.dob.sk/log-malloc2
162162--------------------
163163
164164 * Log to tmpfs, or other FS that handles write operation effectively
165+
165166 If traced application intensively allocates memory, consider logging to tmpf
166- because writting to trace fd is the slowest operation, that is in addition
167+ because writting to trace fd is the slowest operation, that migbt be in addition
167168 protected by a mutex, thus serializing multithreaded memory allocations.
168169
169170
0 commit comments