package Devel::LeakTrace;
use strict;
require 5.008;
use base 'DynaLoader';

    our $VERSION = '0.06';
    bootstrap Devel::LeakTrace $VERSION;





=head1 NAME

Devel::LeakTrace - indicate where leaked variables are coming from.


  perl -MDevel::LeakTrace -e '{ my $foo; $foo = \$foo }'
  leaked SV(0x528d0) from -e line 1
  leaked SV(0x116a10) from -e line 1


Based heavily on Devel::Leak, Devel::LeakTrace uses the pluggable
runops feature found in perl 5.6 and later in order to trace SV
allocations of a running program.

At END time Devel::LeakTrace identifies any remaining variables, and
reports on the lines in which the came into existence.

Note that by default state is first recorded during the INIT phase.
As such the module will not pay attention to any scalars created
during BEGIN time.  This is intentional as symbol table aliasing is
never released before the END times and this is most common in the
implicit BEGIN blocks of C<use> statements.

=head1 CAVEATS

L<glib|> is used for
it's hash manipulation routines to keep state.  This is an external
dependency that is hoped can be removed, but tuits as yet haven't
presented themselves.

=head1 TODO

Elminate dependency on glib

Improve the documentation.

Clustering of reports if they're from the same line.

Stack backtraces to suspect lines.

=head1 AUTHOR

Richard Clamp <> with portions of LeakTrace.xs
taken from Nick Ing-Simmons' Devel::Leak module.


Copyright (C) 2002 Richard Clamp. All Rights Reserved.

This module is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.

=head1 SEE ALSO

L<Devel::Leak>, L<Devel::Cover>