- Log -----------------------------------------------------------------
commit 3188b6e39f995cf3235071eb02ca85f5ab4182db
Author: Rafael Garcia-Suarez <r...@consttype.org>
Date: Tue Nov 24 10:46:21 2009 +0100
Slight rewording of last patch
M pod/perlrun.pod
commit 9aa9f4999e15926df7a18fb2d5cc297f90e02e67
Author: Jim Cromie <jim.c...@gmail.com>
Date: Mon Nov 23 11:57:15 2009 -0700
add mention of PERL_MEM_LOG in perlrun.pod
M pod/perlrun.pod
-----------------------------------------------------------------------
Summary of changes:
pod/perlrun.pod | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/pod/perlrun.pod b/pod/perlrun.pod
index f89c979..b98ab78 100644
--- a/pod/perlrun.pod
+++ b/pod/perlrun.pod
@@ -1245,6 +1245,20 @@ see L<perlsec/"Algorithmic Complexity Attacks"> for more information.
B<Do not disclose the hash seed> to people who don't need to know it.
See also hash_seed() of L<Hash::Util>.
+=item PERL_MEM_LOG
+X<PERL_MEM_LOG>
+
+If your perl was configured with C<-Accflags=-DPERL_MEM_LOG>, setting the
+environment variable C<PERL_MEMLOG> enables logging debug messages. The
+value has the form C<< <number>[m][s][t] >>, where C<number> is the
+filedescriptor number you want to write to, and the combination of letters
+specifies that you want information about (m)emory and/or (s)v, optionally
+with (t)imestamps. For example C<PERL_MEMLOG=1mst> will log all
+information to stdout. You can write to other opened filedescriptors too,
+in a variety of ways;
+
+ bash$ 3>foo3 PERL_MEM_LOG=3m perl ...
+
=item PERL_ROOT (specific to the VMS port)
X<PERL_ROOT>
--
Perl5 Master Repository