1 package Test::Valgrind;
10 use Perl::Destruct::Level level => 3;
12 use Test::Valgrind::Suppressions;
16 Test::Valgrind - Test Perl code through valgrind.
24 our $VERSION = '0.04';
29 eval 'use Test::Valgrind';
30 plan skip_all => 'Test::Valgrind is required to test your distribution with valgrind' if $@;
32 # Code to inspect for memory leaks/errors.
36 This module lets you run some code through the B<valgrind> memory debugger, to test it for memory errors and leaks. Just add C<use Test::Valgrind> at the beginning of the code you want to test. Behind the hood, C<Test::Valgrind::import> forks so that the child can basically C<exec 'valgrind', $^X, $0> (except that of course C<$0> isn't right there). The parent then parses the report output by valgrind and pass or fail tests accordingly.
38 You can also use it from the command-line to test a given script :
40 perl -MTest::Valgrind leaky.pl
44 You can pass parameters to C<import> as a list of key / value pairs, where valid keys are :
52 Also use suppressions from C<$file> besides perl's.
56 C<< no_supp => $bool >>
58 If true, do not use any suppressions.
62 C<< callers => $number >>
64 Specify the maximum stack depth studied when valgrind encounters an error. Raising this number improves granularity. Default is 12.
68 C<< extra => [ @args ] >>
70 Add C<@args> to valgrind parameters.
76 If true, print the raw output of valgrind as diagnostics (may be quite verbose).
80 C<< no_test => $bool >>
82 If true, do not actually output the plan and the tests results.
86 C<< cb => sub { my ($val, $name) = @_; ...; return $passed } >>
88 Specifies a subroutine to execute for each test instead of C<Test::More::is>. It receives the number of bytes leaked in C<$_[0]> and the test name in C<$_[1]>, and is expected to return true if the test passed and false otherwise. Defaults to
92 (defined $_[0] and $_[0] == 0) : 1 : 0
102 (defined $_[0] and $_[0] == 0) ? 1 : 0;
112 croak 'Optional arguments must be passed as key => value pairs' if @_ % 2;
114 if (!defined $args{run} && !$run) {
118 $next = (caller $l++)[1];
119 last unless defined $next;
122 return if not $file or $file eq '-e';
123 my $callers = $args{callers};
124 $callers = 12 unless defined $callers;
125 $callers = int $callers;
126 my $vg = Test::Valgrind::Suppressions::VG_PATH;
127 if (!$vg || !-x $vg) {
128 for (split /:/, $ENV{PATH}) {
136 plan skip_all => 'No valgrind executable could be found in your path';
140 pipe my $rdr, my $wtr or croak "pipe(\$rdr, \$wtr): $!";
144 } elsif ($pid == 0) {
145 setpgrp 0, 0 or croak "setpgrp(0, 0): $!";
146 close $rdr or croak "close(\$rdr): $!";
147 open STDERR, '>&', $wtr or croak "open(STDERR, '>&', \$wtr): $!";
151 '--leak-resolution=high',
152 '--num-callers=' . $callers,
155 unless ($args{no_supp}) {
156 for (Test::Valgrind::Suppressions::supp_path(), $args{supp}) {
157 push @args, '--suppressions=' . $_ if $_;
160 if (defined $args{extra} and ref $args{extra} eq 'ARRAY') {
161 push @args, @{$args{extra}};
164 push @args, '-I' . $_ for @INC;
165 push @args, '-MTest::Valgrind=run,1', $file;
166 print STDERR "valgrind @args\n" if $args{diag};
167 local $ENV{PERL_DESTRUCT_LEVEL} = 3;
168 local $ENV{PERL_DL_NONLAZY} = 1;
171 close $wtr or croak "close(\$wtr): $!";
172 local $SIG{INT} = sub { kill -(SIGTERM) => $pid };
173 plan tests => 5 unless $args{no_test};
176 'definitely lost', 'indirectly lost', 'possibly lost', 'still reachable'
178 my %res = map { $_ => 0 } @tests;
180 diag $_ if $args{diag};
181 if (/^=+\d+=+\s*FATAL\s*:\s*(.*)/) {
183 diag "Valgrind error: $err";
184 $res{$_} = undef for @tests;
186 if (/ERROR\s+SUMMARY\s*:\s+(\d+)/) {
187 $res{errors} = int $1;
188 } elsif (/([a-z][a-z\s]*[a-z])\s*:\s*([\d.,]+)/) {
189 my ($cat, $count) = ($1, $2);
190 if (exists $res{$cat}) {
193 $res{$cat} = int $count;
199 my $cb = ($args{no_test} ? \&_counter
200 : ($args{cb} ? $args{cb} : \&_tester));
202 $failed -= $cb->($res{$_}, 'valgrind ' . $_) ? 1 : 0;
212 You can't use this module to test code given by the C<-e> command-line switch.
214 Results will most likely be better if your perl is built with debugging enabled. Using the latest valgrind available will also help.
216 This module is not really secure. It's definitely not taint safe. That shouldn't be a problem for test files.
218 If your tests output to STDERR, everything will be eaten in the process. In particular, running this module against test files will obliterate their original test results.
222 Valgrind 3.1.0 (L<http://valgrind.org>).
224 L<Carp>, L<POSIX> (core modules since perl 5) and L<Test::More> (since 5.6.2).
226 L<Perl::Destruct::Level>.
230 Vincent Pit, C<< <perl at profvince.com> >>, L<http://www.profvince.com>.
232 You can contact me by mail or on #perl @ FreeNode (vincent or Prof_Vince).
236 Please report any bugs or feature requests to C<bug-test-valgrind at rt.cpan.org>, or through the web interface at L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-Valgrind>. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
240 You can find documentation for this module with the perldoc command.
242 perldoc Test::Valgrind
244 =head1 ACKNOWLEDGEMENTS
246 Rafaƫl Garcia-Suarez, for writing and instructing me about the existence of L<Perl::Destruct::Level> (Elizabeth Mattijsen is a close second).
248 H.Merijn Brand, for daring to test this thing.
250 =head1 COPYRIGHT & LICENSE
252 Copyright 2008 Vincent Pit, all rights reserved.
254 This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
258 1; # End of Test::Valgrind