summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/pods/perlhacktips.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlhacktips.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/pods/perlhacktips.pod12
1 files changed, 7 insertions, 5 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlhacktips.pod b/Master/tlpkg/tlperl/lib/pods/perlhacktips.pod
index 943ad4631b8..bb995f33005 100644
--- a/Master/tlpkg/tlperl/lib/pods/perlhacktips.pod
+++ b/Master/tlpkg/tlperl/lib/pods/perlhacktips.pod
@@ -1,3 +1,4 @@
+
=encoding utf8
=for comment
@@ -203,7 +204,7 @@ Assuming one can dereference any type of pointer for any type of data
long pony = *p; /* BAD */
Many platforms, quite rightly so, will give you a core dump instead of
-a pony if the p happens not be correctly aligned.
+a pony if the p happens not to be correctly aligned.
=item *
@@ -1138,9 +1139,10 @@ finally report any memory problems.
The excellent valgrind tool can be used to find out both memory leaks
and illegal memory accesses. As of version 3.3.0, Valgrind only
-supports Linux on x86, x86-64 and PowerPC. The special "test.valgrind"
-target can be used to run the tests under valgrind. Found errors and
-memory leaks are logged in files named F<testfile.valgrind>.
+supports Linux on x86, x86-64 and PowerPC and Darwin (OS X) on x86 and
+x86-64). The special "test.valgrind" target can be used to run the
+tests under valgrind. Found errors and memory leaks are logged in
+files named F<testfile.valgrind>.
Valgrind also provides a cachegrind tool, invoked on perl as:
@@ -1153,7 +1155,7 @@ of them. Some additional suppressions are defined in F<t/perl.supp>.
To get valgrind and for more information see
- http://developer.kde.org/~sewardj/
+ http://valgrind.org/
=head1 PROFILING