diff --git a/appendices/debugger.xml b/appendices/debugger.xml index 1d0535c7cf..4ce44eb126 100644 --- a/appendices/debugger.xml +++ b/appendices/debugger.xml @@ -1,5 +1,5 @@ - + The PHP Debugger @@ -17,11 +17,12 @@ Using the Debugger - PHP's internal debugger is useful for tracking down evasive bugs. - The debugger works by connecting to a TCP port - for every time PHP starts up. All error messages from that - request will be sent to this TCP connection. This information is - intended for "debugging server" that can run inside an + The internal debugger in PHP 3 is useful for tracking down + evasive bugs. The debugger works by connecting to a + TCP port for every time PHP starts up. + All error messages from that request will be sent to this + TCP connection. This information is intended for + "debugging server" that can run inside an IDE or programmable editor (such as Emacs). @@ -59,11 +60,11 @@ Debugger Protocol - The debugger protocol is line-based. Each line has a + The PHP 3 debugger protocol is line-based. Each line has a type, and several lines compose a - message. Each message starts with a line of + message. Each message starts with a line of the type start and terminates with a line of - the type end. PHP may send lines for different + the type end. PHP 3 may send lines for different messages simultaneously. @@ -116,7 +117,7 @@ type - Type of line. Tells the receiving program about what it + Type of line. Tells the receiving program about what it should treat the following data as: Debugger Line Types @@ -132,19 +133,19 @@ start Tells the receiving program that a debugger message - starts here. The contents of + starts here. The contents of data will be the type of error message, listed below. message - The PHP error message. + The PHP 3 error message. location - File name and line number where the error occured. The + File name and line number where the error occured. The first location line will always contain the top-level location. data will contain @@ -157,7 +158,7 @@ frames Number of frames - in the following stack dump. If there are four frames, + in the following stack dump. If there are four frames, expect information about four levels of called functions. If no "frames" line is given, the depth should be assumed to be 0 (the error occured at top-level). @@ -167,7 +168,7 @@ function - Name of function where the error occured. Will be + Name of function where the error occured. Will be repeated once for every level in the function call stack.