libtest-valgrind-perl 1.19-1 source package in Ubuntu

Changelog

libtest-valgrind-perl (1.19-1) unstable; urgency=medium

  [ Salvatore Bonaccorso ]
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
  * debian/upstream/metadata: change GitHub/CPAN URL(s) to HTTPS.
  * Import upstream version 1.19.
    Closes: #832833
  * Update years of upstream and packaging copyright.
  * Add more typos to debian/patches/typo.patch.
  * Declare compliance with Debian Policy 3.9.8.

 -- gregor herrmann <email address hidden>  Mon, 01 Aug 2016 23:32:21 +0200

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release universe perl
Bionic release universe perl

Builds

Yakkety: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libtest-valgrind-perl_1.19-1.dsc 2.4 KiB 0d02da7b1a4a52768db1f14e9f3705d6937e0f28307422639b1c185e7447d5e1
libtest-valgrind-perl_1.19.orig.tar.gz 52.3 KiB 1838a7a15fee7a8f069e4e6b461c5e169058b615b8dfb43784b3d5da1a60811b
libtest-valgrind-perl_1.19-1.debian.tar.xz 4.3 KiB e810405d32ac90f88d005e688ec8a49dc45b2b7a4aa9f89b98f306eb3428f453

Available diffs

No changes file available.

Binary packages built by this source

libtest-valgrind-perl: 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.