aboutsummaryrefslogtreecommitdiff
path: root/development/xdebug/README
diff options
context:
space:
mode:
authorHeinz Wiesinger <pprkut@liwjatan.at>2012-04-22 12:29:48 -0400
committerdsomero <xgizzmo@slackbuilds.org>2012-04-22 12:29:48 -0400
commit4396f3007ba0f61addaedf2961d3f5e4d135f7d0 (patch)
tree1341290c202e8501d3a9e5e5ad602ccc032b6d40 /development/xdebug/README
parentdfb9003fd962b26f5565ee7754d7fc8678bfca9e (diff)
development/xdebug: Updated for version 2.1.4.
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Diffstat (limited to 'development/xdebug/README')
-rw-r--r--development/xdebug/README12
1 files changed, 6 insertions, 6 deletions
diff --git a/development/xdebug/README b/development/xdebug/README
index e013cddff873..9d9c7d2a8094 100644
--- a/development/xdebug/README
+++ b/development/xdebug/README
@@ -1,10 +1,10 @@
Xdebug (A PHP extension for debugging PHP scripts)
-The Xdebug extension helps you debugging your script by providing a lot of
-valuable debug information. The debug information that Xdebug can provide
-includes the following: stack traces and function traces in error messages,
-memory allocation and protection for infinite recursions. Xdebug also
-provides profiling information for PHP, scripts, code coverage analysis and
+The Xdebug extension helps you debugging your script by providing a lot of
+valuable debug information. The debug information that Xdebug can provide
+includes the following: stack traces and function traces in error messages,
+memory allocation and protection for infinite recursions. Xdebug also
+provides profiling information for PHP, scripts, code coverage analysis and
capabilities to debug PHP scripts interactively with a debug client.
This requires libedit.
@@ -12,7 +12,7 @@ This requires libedit.
Once you've installed xdebug, uncomment the following line in /etc/php/xdebug.ini:
; zend_extension = "/usr/lib/php/extensions/xdebug.so"
-Restart your webserver if you're using php with it, and as a recomendation
+Restart your webserver if you're using php with it, and as a recomendation
from xdebug's README: "Write a PHP page that calls "phpinfo();" Load it
in a browser and look for the info on the xdebug module. If you see it,
you have been successful!"