| 1 |
Source: libtest-valgrind-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: gregor herrmann <[email protected]>, |
| 4 |
Florian Schlichting <[email protected]> |
| 5 |
Section: perl |
| 6 |
Testsuite: autopkgtest-pkg-perl |
| 7 |
Priority: optional |
| 8 |
Build-Depends: debhelper-compat (= 13) |
| 9 |
Build-Depends-Indep: libenv-sanctify-perl <!nocheck>, |
| 10 |
libfile-homedir-perl <!nocheck>, |
| 11 |
libperl-destruct-level-perl <!nocheck>, |
| 12 |
libxml-twig-perl <!nocheck>, |
| 13 |
perl-xs-dev, |
| 14 |
perl:native, |
| 15 |
valgrind-if-available <!nocheck> |
| 16 |
Standards-Version: 4.7.2 |
| 17 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libtest-valgrind-perl |
| 18 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libtest-valgrind-perl.git |
| 19 |
Homepage: https://metacpan.org/release/Test-Valgrind |
| 20 |
Rules-Requires-Root: no |
| 21 |
|
| 22 |
Package: libtest-valgrind-perl |
| 23 |
Architecture: all |
| 24 |
Depends: ${misc:Depends}, |
| 25 |
${perl:Depends}, |
| 26 |
libenv-sanctify-perl, |
| 27 |
libfile-homedir-perl, |
| 28 |
libperl-destruct-level-perl, |
| 29 |
libxml-twig-perl, |
| 30 |
valgrind |
| 31 |
Description: module to test Perl code through valgrind |
| 32 |
Test::Valgrind is a module that lets you run Perl code through the memcheck |
| 33 |
tool of the Valgrind Memory Debugger, to test it for memory errors and leaks. |
| 34 |
. |
| 35 |
Due to the nature of perl's memory allocator, this module can't track leaks |
| 36 |
of Perl objects. This includes non-mortalized scalars and memory cycles. |
| 37 |
However, it can track leaks of chunks of memory allocated in XS extensions |
| 38 |
with Newx and friends or malloc. As such, it's complementary to the other |
| 39 |
very good leak detectors such as Test::LeakTrace. |
| 40 |
. |
| 41 |
Additionally, this module can run arbitrary commands (not just Perl code) |
| 42 |
and provide output compliant with Perl's Test Anything Protocol (TAP). |
| 43 |
This means that any executable can be run under valgrind and incorporated |
| 44 |
into your testsuite. |