summaryrefslogtreecommitdiff
path: root/devel/lmdbg
AgeCommit message (Collapse)AuthorFilesLines
2017-01-19Convert all occurrences (353 by my count) ofagc1-3/+3
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.
2015-11-03Add SHA512 digests for distfiles for devel categoryagc1-1/+2
Issues found with existing distfiles: distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip distfiles/fortran-utils-1.1.tar.gz distfiles/ivykis-0.39.tar.gz distfiles/enum-1.11.tar.gz distfiles/pvs-3.2-libraries.tgz distfiles/pvs-3.2-linux.tgz distfiles/pvs-3.2-solaris.tgz distfiles/pvs-3.2-system.tgz No changes made to these distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-01-04Use BROKEN_ON_PLATFORM for undocumented MacOS restriction.dholland1-2/+2
2014-02-05Update to 1.2.1cheusov2-6/+6
lmdbg-leaks: fix incorrect memory leak detection with calloc(3).
2013-08-07Update to 1.2.0cheusov3-11/+14
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.
2012-10-31Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2012-09-02Update to 1.1.0cheusov3-8/+9
Fix in regression tests. Now "make test" exits with non-zero status if something fails. lmdbg-run: - Zero addresses are removed from stacktraces generated by glibc's backtrace(3). This fixes asserts in lmdbg-stat(1). - Double "0x" in "info section" were fixed (seen on NetBSD). - backtrace(3) from libexecinfo is used instead of builtin implementation if the library and execinfo.h are available (FreeBSD, NetBSD). lmdbg-sym: - Fixes. Sometimes addresses were converted to symbols incorrectly. The problem was seen on modern Linux distros with recent gdb(1). lmdbg-stat: - Now incompletly read lines (having no LF in the end) are ignored. This fixes crashes and therefore empty output or lmdbg(1) when analysed program is killed. - Alternative implementation written in awk was removed. Build infrastructure was converted to 2-level dirs. This requires mk-configure>=0.23.0 for build. Minor clean-ups in man pages and Makefiles.
2012-03-09clean-ups (adapted for recent mk-configure)cheusov1-4/+2
2012-01-09Update to lmdbg-1.0.0cheusov3-16/+11
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.
2011-12-02Update to 0.17.0cheusov3-15/+13
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-11-26clang was added to a list of supported compilerscheusov1-3/+3
minor code clean-ups
2011-10-19Adding MANDIR to MAKE_ENV is not needed anymorecheusov1-3/+1
2011-10-09Update my emailcheusov1-2/+2
2011-09-04For all packages based on mk-configure "configure" target is provided.cheusov1-4/+5
This fixes parallel builds.
2011-07-03Using REPLACE_INTERPRETER does not magically generate a dependence on thedholland1-2/+3
interpreter. Depend explicitly on lang/runawk. PKGREVISION++
2011-05-10fix #!/usr/bin/env issuecheusov1-1/+6
2011-05-08LMDBG is a collection of small tools for collecting and analyzing logscheusov4-0/+94
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