kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/lmdbg/Makefile

40 lines
1 KiB
Makefile
Raw Normal View History

Follow some http redirects.
2017-08-16 22:21:03 +02:00
# $NetBSD: Makefile,v 1.17 2017/08/16 20:21:08 wiz Exp $
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
#
Update to 1.2.1 lmdbg-leaks: fix incorrect memory leak detection with calloc(3).
2014-02-05 22:14:00 +01:00
DISTNAME= lmdbg-1.2.1
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
CATEGORIES= devel
Convert all occurrences (353 by my count) of MASTER_SITES= site1 \ site2 style continuation lines to be simple repeated MASTER_SITES+= site1 MASTER_SITES+= site2 lines. As previewed on tech-pkg. With thanks to rillig for fixing pkglint accordingly.
2017-01-19 19:52:01 +01:00
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=lmdbg/}
MASTER_SITES+= http://mova.org/~cheusov/pub/lmdbg/
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
Update my email
2011-10-09 12:02:44 +02:00
MAINTAINER= cheusov@NetBSD.org
Follow some http redirects.
2017-08-16 22:21:03 +02:00
HOMEPAGE= https://sourceforge.net/projects/lmdbg/
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
COMMENT= Lightweight Modular malloc Debugger
For all packages based on mk-configure "configure" target is provided. This fixes parallel builds.
2011-09-04 20:21:26 +02:00
LICENSE= mit
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
Update to 1.2.0 New tool lmdbg-head(1) was implemented, see the man page for details. README: recomendations for procfs lmdbg-sym: - Much simplier (and correct) method for address convertion was implemented. As a result lmdbg-sym works correctly on AltLinux where ASLR and PIE are enabled by default. - Breakpoint are removed very soon after creation. This saves a lot of memory consumed by gdb(1) and dramatically speeds up it. lmdbg-run: - Arguments are passed correctly to progname - On glibc-based systems (e.g. Linux) malloc hooks are not used anymore as they are declared deprecated - Addresses from lmdbg.c are not included to stacktrace - Additional checks for address (returned by stacktrace(3)) correctness. As a result gdb(1) doesn't crash and therefore lmdbg-sym(1) work correctly. - stacktrace(3) doesn't not crash anymore on NetBSD/x64_64 with system utilities. See implementation details in stacktrace.c. - New option -N - Option -v works correctly with non-zero exit status of progname. - Exits with error if progname is not specified. lmdbg-stat: - Fix for NULL dereference appeared if free(3) or realloc(3) stacktrace is seen without appropriate malloc(3) stacktrace. AWK interpreter is found at configure time via MKC_REQUIRE_PROGS. Build and regression tests were fixed for non-empty MAKEOBJDIR case. ChangeLog file is never installed. lmdbg-s2m and lmsbg-m2s was moved to libexec dir. mk-configure >= 0.24.0 is required for build. Fixes, improvements and additions in regression tests.
2013-08-07 23:07:25 +02:00
BUILD_DEPENDS+= mk-configure>=0.24.0:../../devel/mk-configure
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
DEPENDS+= pipestatus-[0-9]*:../../devel/pipestatus
clang was added to a list of supported compilers minor code clean-ups
2011-11-26 11:18:49 +01:00
DEPENDS+= runawk>=1.3.1:../../lang/runawk
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
#DEPENDS+= gdb-[0-9]*:../../devel/gdb
clang was added to a list of supported compilers minor code clean-ups
2011-11-26 11:18:49 +01:00
ONLY_FOR_COMPILER= gcc icc clang
Use BROKEN_ON_PLATFORM for undocumented MacOS restriction.
2015-01-04 03:47:06 +01:00
BROKEN_ON_PLATFORM= Darwin-*-*
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
TEST_TARGET= test
Update to 0.17.0 Long options have been removed from all programs. Use standard single-letter POSIX-compatible options. lmdbg-sym: - Doesn't accept progname as an argument anymore. Use -P option instead. - option --with-so was replaced with -s. SORRY FOR INCOMPATIBILITIES WITH PREVIOUS RELEASES. ---------------------------------- lmdbg: - -M option was added. lmdbg(1) is now a meta tools which is able to not only collecting memory leaks. See the manual page for details. - -n option was added - -T and -B options were added - Regression tests were added for -M A lot of improvements and grammar fixes in manual pages. Thanks to Nikolai Krot for this. lmdbg-stat, tests/test.sh: - Fixes for Solaris lmdbg-run: - options -T and -B were added to lmdbg-run. - option -n was added. It disables logging on startup. Sending SIGUSR1 signal to the process enables it. -f option was added, synonym for -p. lmdbg-grep.1: - documentation for "bytes" variable If set, LMDBG_MODULES_AWK and LMDBG_STRIP_AWK environment variables are used as a path to AWK interpreter by "lmdbg-modules" and "lmdbg-strip" programs respectively. More regression tests
2011-12-02 23:45:47 +01:00
REPLACE_SH= scripts/lmdbg*.in tests/test.sh
fix #!/usr/bin/env issue
2011-05-10 10:10:13 +02:00
REPLACE_INTERPRETER+= runawk
REPLACE.runawk.old= .*runawk
REPLACE.runawk.new= ${PREFIX}/bin/runawk
REPLACE_FILES.runawk= scripts/lmdbg-*.in
Update to 1.2.0 New tool lmdbg-head(1) was implemented, see the man page for details. README: recomendations for procfs lmdbg-sym: - Much simplier (and correct) method for address convertion was implemented. As a result lmdbg-sym works correctly on AltLinux where ASLR and PIE are enabled by default. - Breakpoint are removed very soon after creation. This saves a lot of memory consumed by gdb(1) and dramatically speeds up it. lmdbg-run: - Arguments are passed correctly to progname - On glibc-based systems (e.g. Linux) malloc hooks are not used anymore as they are declared deprecated - Addresses from lmdbg.c are not included to stacktrace - Additional checks for address (returned by stacktrace(3)) correctness. As a result gdb(1) doesn't crash and therefore lmdbg-sym(1) work correctly. - stacktrace(3) doesn't not crash anymore on NetBSD/x64_64 with system utilities. See implementation details in stacktrace.c. - New option -N - Option -v works correctly with non-zero exit status of progname. - Exits with error if progname is not specified. lmdbg-stat: - Fix for NULL dereference appeared if free(3) or realloc(3) stacktrace is seen without appropriate malloc(3) stacktrace. AWK interpreter is found at configure time via MKC_REQUIRE_PROGS. Build and regression tests were fixed for non-empty MAKEOBJDIR case. ChangeLog file is never installed. lmdbg-s2m and lmsbg-m2s was moved to libexec dir. mk-configure >= 0.24.0 is required for build. Fixes, improvements and additions in regression tests.
2013-08-07 23:07:25 +02:00
MAKE_ENV+= AWK=${AWK:Q}
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
post-install:
Update to lmdbg-1.0.0 libstacktrace: Remove signal handlers and other garbage. All we need is __builtin_frame_address and __builtin_return_address builtins and nothing else. Documentation files have been moved to subproject "doc". Run "mkcmake install-doc" for installing it (or change SUBPRJ_DFLT). Only backtrace(3) in libc is accepted as an external implementation of stacktrace(3). This may fix build failure on FreeBSD with installed libexeinfo.
2012-01-09 20:47:35 +01:00
cd ${WRKSRC} && \
${MAKE_ENV} ${MAKE_PROGRAM} ${INSTALL_MAKE_FLAGS} install-doc
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
clean-ups (adapted for recent mk-configure)
2012-03-09 19:58:19 +01:00
.include "../../devel/mk-configure/mk-c.mk"
LMDBG is a collection of small tools for collecting and analyzing logs of malloc/realloc/memalign/free etc. function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks. Unlike some others LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze application on a per-module basis. Simple but powerful tools for analisis are also provided. lmdbg-run - Creates malloc/realloc/free/memalign/... logs lmdbg-sym - Converts addresses to 'file.c:NUM func_name' lmdbg-leak - Checks for memory leaks lmdbg-stat - Gathers statistical information about memory allocations lmdbg-grep - Greps the stackframes lmdbg-strip - Strips the stackframes lmdbg-module - Enrichs the stackframes with a module name lmdbg-sort - Sorts the stackframes by e.g. total allocated bytes, a number of memory allocations etc. lmdbg-sysleaks - Filters out system memory leaks e.g. libc's
2011-05-08 20:32:15 +02:00
.include "../../devel/libjudy/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink