Package: leaktracer Version: 2.4-6 Severity: minor File: /usr/share/man/man1/leak-analyze.1.gz
The manual page contains incorrect info about how to run leak-analyze: leak-analyze program [ leak.out ] [ main ] [ program arguments ... ] The README & code make it clear the correct way to call leak-analyze is: leak-analyze program [ leak.out [ breakpoint [ program arguments ... ] ] ] The two issues are that: * the third argument is the breakpoint but 'main' doesn't really explain that well enough * the arguments are not independent, you have to specify prior ones before you can specify latter ones but the pattern of [] characters seems to indicate that they can be specified independently -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages leaktracer depends on: ii gdb 7.12-6 ii libc6 2.24-10 ii libgcc1 1:6.3.0-16 ii libstdc++6 6.3.0-16 ii perl 5.24.1-2 leaktracer recommends no packages. leaktracer suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
