Revision history for Test-Valgrind
+1.02 2009-05-02 12:05 UTC
+ + Add : Commands can now be aggregated.
+ + Add : The commands can now also filter and mangle reports.
+ + Chg : The perl suppressions are now stripped from everything below
+ Perl_runops_*.
+ + Doc : Typos, nits and clarifications.
+
1.01 2009-04-14 21:15 UTC
+ Add : Allow testing code given by -e. Hurray for source filters!
+ Fix : Lazily load version.pm in Test::Valgrind::Session so that it's
--- #YAML:1.0
name: Test-Valgrind
-version: 1.01
-abstract: Test Perl code through valgrind.
+version: 1.02
+abstract: Generate suppressions, analyse and test any command with valgrind.
author:
- Vincent Pit <perl@profvince.com>
license: perl
bugtracker: http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-Valgrind
homepage: http://search.cpan.org/dist/Test-Valgrind/
license: http://dev.perl.org/licenses/
- repository: http://git.profvince.com/perl/modules/Test-Valgrind.git
+ repository: http://git.profvince.com/?p=perl%2Fmodules%2FTest-Valgrind.git
no_index:
directory:
- t
NAME
- Test::Valgrind - Test Perl code through valgrind.
+ Test::Valgrind - Generate suppressions, analyse and test any command
+ with valgrind.
VERSION
- Version 1.01
+ Version 1.02
SYNOPSIS
# From the command-line
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. It allows you to run
+ *any* executable under valgrind, generate the corresponding suppressions
+ and convert the analysis output to TAP so that it can be incorporated
+ into your project's testsuite.
+
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
"import [ %options ]"
In the parent process, "import" calls "analyse" with the arguments it
received itself - except that if no "file" option was supplied, it tries
- to pick the highest caller context that looks like a script. When the
- analyse finishes, it exists with the status that was returned.
+ to pick the first caller context that looks like a script. When the
+ analyse ends, it exits with the status that was returned.
In the child process, it just "return"s so that the calling code is
actually run under "valgrind".
VARIABLES
$dl_unload
When set to true, all dynamic extensions that were loaded during the
- analysis will be unloaded at "END" time by DynaLoader::dl_unload_file.
+ analysis will be unloaded at "END" time by "dl_unload_file" in
+ DynaLoader.
Since this obfuscates error stack traces, it's disabled by default.