What I can't get working is the extended debugging promised by the Devel::Leak documentation. All I get is a count, and from CheckSV, the cryptic "new 0x5a18b0".
#! /usr/bin/debugperl -w
use strict;
use warnings;
use Devel::Leak;
my $foo;
my $countdown = 10;
while($countdown--) {
my $count = Devel::Leak::NoteSV($foo);
print "$count";
<>;
my $bar;
$bar = \$bar;
}
my $count = Devel::Leak::CheckSV($foo);
print "End $count\n";
Prints
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
new 0x5a18b0 :
End 2610
Even though I've got a debugging perl from Debian:
debugperl -V
Summary of my perl5 (revision 5 version 8 subversion 8) Characteristic
+s of this binary (from libperl):
Compile-time options: DEBUGGING MULTIPLICITY PERL_IMPLICIT_CONTEXT
PERL_MALLOC_WRAP THREADS_HAVE_PIDS USE_64_BIT_
+ALL
USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES
USE_PERLIO USE_REENTRANT_API
What I can't get working is the sv_dump() mentioned in the Devel::Leak documentation. And when I'm debugging a 100000+ line plus application, that will be crucial.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|