This website works better with JavaScript.
Explore
Help
Sign In
rpms
/
perl-Test-Valgrind
Watch
21
Star
0
Fork
You've already forked perl-Test-Valgrind
0
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
eadd866cad
i9ce
i9
epel9
changed/i9/perl-Test-Valgrind-1.19-22.el9
changed/i9ce/perl-Test-Valgrind-1.19-17.el9
imports/e9/perl-Test-Valgrind-1.19-17.el9
Branches
Tags
${ item.name }
Create tag
${ searchTerm }
Create branch
${ searchTerm }
from 'eadd866cad'
${ noResults }
perl-Test-Valgrind
/
.gitignore
2 lines
30 B
Raw
Normal View
History
Unescape
Escape
Initial import (perl-Test-Valgrind-1.13-3) The Test::Valgrind::* API lets you run Perl code through the memcheck tool of the valgrind memory debugger, to test for memory errors and leaks. The Test::Valgrind module itself is a front-end to this API. If they aren't available yet, it will first generate suppressions for the current perl interpreter and store them in the portable flavor of ~/.perl/Test-Valgrind/suppressions/$VERSION. The actual run will then take place, and tests will be passed or failed according to the result of the analysis. The complete API is much more versatile than this. By declaring an appropriate Test::Valgrind::Command class, you can run any executable (that is, not only Perl scripts) under valgrind, generate the corresponding suppressions on-the-fly and convert the analysis result to TAP output so that it can be incorporated into your project's test suite. If you're not interested in producing TAP, you can output the results in whatever format you like (for example HTML pages) by defining your own Test::Valgrind::Action class.
13 years ago
/Test-Valgrind-[0-9.]*.tar.gz