summaryrefslogtreecommitdiff
path: root/Porting/pumpkin.pod
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2013-06-20 10:01:20 +0200
committerNicholas Clark <nick@ccl4.org>2013-07-01 11:14:48 +0200
commit16fb77a82988e440fb4a6adad6c5fe7b09512f14 (patch)
treeb58644441f55205d11ae51a9e1f4e9f3a9957e7f /Porting/pumpkin.pod
parent463c96de11efb9662169e0bf06f1faf33464a4cf (diff)
downloadperl-16fb77a82988e440fb4a6adad6c5fe7b09512f14.tar.gz
Remove the explicit purify/quantify/purecov targets and documentation.
It's not clear whether IBM still sell quantify or purecov. They still seem to sell purify, but I'm not sure if anyone is using it these days to detect bugs in perl. This doesn't prevent anyone from using these tools if they have them, as it's still possible to run the commands by "hand". But by removing probably unused code and documentation, the signal to noise ratio improves.
Diffstat (limited to 'Porting/pumpkin.pod')
-rw-r--r--Porting/pumpkin.pod36
1 files changed, 0 insertions, 36 deletions
diff --git a/Porting/pumpkin.pod b/Porting/pumpkin.pod
index 89c5a46863..a8c8fb0efd 100644
--- a/Porting/pumpkin.pod
+++ b/Porting/pumpkin.pod
@@ -651,42 +651,6 @@ things.
=back
-=head1 Running Purify
-
-Purify is a commercial tool that is helpful in identifying memory
-overruns, wild pointers, memory leaks and other such badness. Perl
-must be compiled in a specific way for optimal testing with Purify.
-
-Use the following commands to test perl with Purify:
-
- sh Configure -des -Doptimize=-g -Uusemymalloc \
- -Dusemultiplicity -Accflags=-DPURIFY
- setenv PURIFYOPTIONS "-chain-length=25"
- make all pureperl
- cd t
- ln -s ../pureperl perl
- setenv PERL_DESTRUCT_LEVEL 2
- ./perl TEST
-
-Disabling Perl's malloc allows Purify to monitor allocations and leaks
-more closely; using Perl's malloc will make Purify report most leaks
-in the "potential" leaks category. Enabling the multiplicity option
-allows perl to clean up thoroughly when the interpreter shuts down, which
-reduces the number of bogus leak reports from Purify. The -DPURIFY
-enables any Purify-specific debugging code in the sources.
-
-Purify outputs messages in "Viewer" windows by default. If you don't have
-a windowing environment or if you simply want the Purify output to
-unobtrusively go to a log file instead of to the interactive window,
-use the following options instead:
-
- setenv PURIFYOPTIONS "-chain-length=25 -windows=no \
- -log-file=perl.log -append-logfile=yes"
-
-The only currently known leaks happen when there are compile-time errors
-within eval or require. (Fixing these is non-trivial, unfortunately, but
-they must be fixed eventually.)
-
=head1 Common Gotchas
=over 4