File: control

package info (click to toggle)
libtest-valgrind-perl 1.19-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, stretch
  • size: 416 kB
  • ctags: 228
  • sloc: perl: 2,777; makefile: 17
file content (43 lines) | stat: -rw-r--r-- 1,909 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Source: libtest-valgrind-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Jonathan Yu <jawnsy@cpan.org>,
           gregor herrmann <gregoa@debian.org>,
           Florian Schlichting <fschlich@zedat.fu-berlin.de>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper (>= 9.20120312~)
Build-Depends-Indep: perl,
                     libenv-sanctify-perl,
                     libfile-homedir-perl,
                     libperl-destruct-level-perl,
                     libxml-twig-perl,
                     valgrind
Standards-Version: 3.9.8
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libtest-valgrind-perl.git
Vcs-Git: https://anonscm.debian.org/git/pkg-perl/packages/libtest-valgrind-perl.git
Homepage: https://metacpan.org/release/Test-Valgrind

Package: libtest-valgrind-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libenv-sanctify-perl,
         libfile-homedir-perl,
         libperl-destruct-level-perl,
         libxml-twig-perl,
         valgrind
Description: module to test Perl code through valgrind
 Test::Valgrind is a module that lets you run Perl code through the memcheck
 tool of the Valgrind Memory Debugger, to test it for memory errors and leaks.
 .
 Due to the nature of perl's memory allocator, this module can't track leaks
 of Perl objects. This includes non-mortalized scalars and memory cycles.
 However, it can track leaks of chunks of memory allocated in XS extensions
 with Newx and friends or malloc. As such, it's complementary to the other
 very good leak detectors such as Test::LeakTrace.
 .
 Additionally, this module can run arbitrary commands (not just Perl code)
 and provide output compliant with Perl's Test Anything Protocol (TAP).
 This means that any executable can be run under valgrind and incorporated
 into your testsuite.