diff options
| author | Alexey Dokuchaev <danfe@FreeBSD.org> | 2011-08-18 08:18:53 +0000 |
|---|---|---|
| committer | Alexey Dokuchaev <danfe@FreeBSD.org> | 2011-08-18 08:18:53 +0000 |
| commit | 1c81270cfc936df13c7060e60fdd3990c0a6e4b9 (patch) | |
| tree | 10351d878d4cb598ea039bcb12a03f13ed6980fd /devel | |
| parent | c23e369a3f881002e00efcdadeee75b2ece12cb1 (diff) | |
Notes
Diffstat (limited to 'devel')
| -rw-r--r-- | devel/leaktracer/Makefile | 9 | ||||
| -rw-r--r-- | devel/leaktracer/pkg-descr | 19 |
2 files changed, 13 insertions, 15 deletions
diff --git a/devel/leaktracer/Makefile b/devel/leaktracer/Makefile index bd42522bbe4c..ac6325368fab 100644 --- a/devel/leaktracer/Makefile +++ b/devel/leaktracer/Makefile @@ -12,7 +12,7 @@ MASTER_SITES= http://www.andreasen.org/LeakTracer/ \ http://freebsd.nsu.ru/distfiles/ DISTNAME= LeakTracer -MAINTAINER= danfe@FreeBSD.org +MAINTAINER= ports@FreeBSD.org COMMENT= Trace and analyze memory leaks in C++ programs USE_LDCONFIG= yes @@ -24,13 +24,12 @@ PLIST_FILES= bin/LeakCheck bin/leak-analyze lib/LeakTracer.so PORTDOCS= README README.html do-install: - ${INSTALL_SCRIPT} ${WRKSRC}/LeakCheck ${PREFIX}/bin - ${INSTALL_SCRIPT} ${WRKSRC}/leak-analyze ${PREFIX}/bin + ${INSTALL_SCRIPT} ${WRKSRC}/LeakCheck ${WRKSRC}/leak-analyze \ + ${PREFIX}/bin ${INSTALL_PROGRAM} ${WRKSRC}/LeakTracer.so ${PREFIX}/lib .if !defined(NOPORTDOCS) @${MKDIR} ${DOCSDIR} - ${INSTALL_DATA} ${WRKSRC}/README ${DOCSDIR} - ${INSTALL_DATA} ${WRKSRC}/README.html ${DOCSDIR} + ${INSTALL_DATA} ${WRKSRC}/README ${WRKSRC}/README.html ${DOCSDIR} .endif .include <bsd.port.mk> diff --git a/devel/leaktracer/pkg-descr b/devel/leaktracer/pkg-descr index ab0ca2f1401d..b321de2267e4 100644 --- a/devel/leaktracer/pkg-descr +++ b/devel/leaktracer/pkg-descr @@ -1,15 +1,14 @@ -LeakTracer is a small tool for checking a C++ program for memory leaks. +LeakTracer is a small tool for checking C++ programs for memory leaks. Run +your program using the provided LeakCheck script. It uses the LD_PRELOAD +feature to "overlay" some functions on top of your functions (no recompile +needed). -To use LeakTracer, run your program using the provided LeakCheck script. It -uses the LD_PRELOAD feature to "overlay" some functions on top of your -functions (no recompile needed). +LeakTracer uses gdb to print out the exact line where memory was allocated +but not freed -- this means you have to free all dynamically allocated data. +LeakTracer also overrides the global operator new and operator delete -- +this will give problems if you override them as well. -LeakTracer uses gdb to print out the exact line where the memory was allocated -and not freed -- this of course means you have to free all dynamically -allocated data. LeakTracer also overrides the global operator new and operator -delete -- this will give problems if you override them as well. - -LeakTracer traces only new/new[] and delete calls -- it does not look at +LeakTracer traces only new/delete calls; it does not look at traditional malloc/free/realloc. WWW: http://www.andreasen.org/LeakTracer/ |