From: David Mitchell <davem@iabyn.com>
Date: Mon, 20 Jul 2009 12:51:56 +0000 (+0100)
Subject: Mention DTrace in INSTALL.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=1db12997af352ff571bae72090309d21832cdd02;p=p5sagit%2Fp5-mst-13.2.git

Mention DTrace in INSTALL.
Also explain that a debugging build is slower
---

diff --git a/INSTALL b/INSTALL
index 50eeea6..89707cf 100644
--- a/INSTALL
+++ b/INSTALL
@@ -905,6 +905,22 @@ Removes -g from optimize, and -DDEBUGGING from ccflags.
 If you are using a shared libperl, see the warnings about multiple
 versions of perl under L<Building a shared Perl library>.
 
+Note that a perl built with -DDEBUGGING will be bigger and will run more
+slowly than a standard perl.
+
+=head2 DTrace support
+
+On platforms where DTrace is available, it may be enabled by 
+using the -Dusedtrace option to Configure. DTrace probes are available for
+subroutine entry (sub-entry) and subroutine exit (sub-exit). Here's a
+simple D script that uses them:
+
+  perl$target:::sub-entry, perl$target:::sub-return {
+    printf("%s %s (%s:%d)\n", probename == "sub-entry" ? "->" : "<-",
+              copyinstr(arg0), copyinstr(arg1), arg2);
+  }
+
+
 =head2 Extensions
 
 Perl ships with a number of standard extensions.  These are contained