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

32 lines
633 B
Text
Raw Normal View History

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
@comment $NetBSD: PLIST,v 1.4 2013/08/07 21:07:25 cheusov 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
bin/lmdbg
bin/lmdbg-grep
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
bin/lmdbg-head
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
bin/lmdbg-leaks
bin/lmdbg-modules
bin/lmdbg-run
bin/lmdbg-sort
bin/lmdbg-stat
bin/lmdbg-strip
bin/lmdbg-sym
bin/lmdbg-sysleaks
lib/liblmdbg.a
lib/liblmdbg.so
lib/liblmdbg.so.0
lib/liblmdbg.so.0.0
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
libexec/lmdbg/lmdbg-m2s
libexec/lmdbg/lmdbg-s2m
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
man/man1/lmdbg-grep.1
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
man/man1/lmdbg-head.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
man/man1/lmdbg-leaks.1
man/man1/lmdbg-run.1
man/man1/lmdbg-sort.1
man/man1/lmdbg-stat.1
man/man1/lmdbg-sym.1
man/man1/lmdbg-sysleaks.1
man/man1/lmdbg.1
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
share/doc/lmdbg/LICENSE
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
share/doc/lmdbg/NEWS
share/doc/lmdbg/README
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
share/doc/lmdbg/TODO
Reference in a new issue Copy permalink