From 535988bf7dd89740daa17ed05cae12d5e63b143b Mon Sep 17 00:00:00 2001 From: Egon Schmid Date: Mon, 24 Jan 2000 21:01:18 +0000 Subject: [PATCH] Made it a little bit more readable for translators. git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@18805 c90b9560-bf6c-de11-be94-00142212c4b1 --- appendices/debugger.xml | 413 +++++++++++++++++++++------------------- 1 file changed, 222 insertions(+), 191 deletions(-) diff --git a/appendices/debugger.xml b/appendices/debugger.xml index 032344fcb7..652212b840 100644 --- a/appendices/debugger.xml +++ b/appendices/debugger.xml @@ -1,200 +1,231 @@ - - The PHP Debugger + + The PHP Debugger - - Using the Debugger + + 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 - IDE or programmable editor (such as Emacs). - - - How to set up the debugger: - - Set up a TCP port for the debugger in the configuration file (debugger.port) and enable it - (debugger.enabled). - - Set up a TCP listener on that port somewhere - (for example socket -l -s 1400 on UNIX). - - In your code, run - "debugger_on(host)", where - host is the IP number or name of the - host running the TCP listener. - - - - Now, all warnings, notices etc. will show up on that listener - socket, even if you them turned off with - error_reporting. - - - Debugger Protocol - - The debugger protocol is line-based. Each line has a - type, and several lines compose a - 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 - messages simultaneously. - - - A line has this format: - - -date time host(pid) type: message-data - - - - - date + + 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 + IDE or programmable editor (such as Emacs). + + + How to set up the debugger: + - Date in ISO 8601 format (yyyy-mm-dd) + + Set up a TCP port for the debugger in the configuration file (debugger.port) and enable it + (debugger.enabled). - - - time - Time including microseconds: - hh:mm:uuuuuu + + Set up a TCP listener on that port somewhere (for example + socket -l -s 1400 on UNIX). - - - host - DNS name or IP address of the host where the script - error was generated. + + In your code, run + "debugger_on(host)", where + host is the IP number or name of the + host running the TCP listener. + - - - pid - - PID (process id) on host of - the process with the PHP script that generated this error. - - - - type - - Type of line. Tells the receiving program about what - it should treat the following data as: - - Debugger Line Types - - - - Name - Meaning - - - - - start Tells the - receiving program that a debugger message starts here. - The contents of data will be - the type of error message, listed below. - - - - message - The PHP error message. - - - location - - File name and line number where the error occured. The - first location line will always contain - the top-level location. data - will contain - file:line. - There will always be a location line - after message and after every - function. - - - - frames Number of - 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). - - - - function Name of - function where the error occured. Will be repeated once - for every level in the function call stack. - - - end Tells the - receiving program that a debugger message ends - here. - - - -
- - - - - data - - Line data. - - - + + Now, all warnings, notices etc. will show up on that listener + socket, even if you them turned off with + error_reporting. + + - - Debugger Error Types - - - - Debugger - PHP Internal - - - - - warning - E_WARNING - - - error - E_ERROR - - - parse - E_PARSE - - - notice - E_NOTICE - - - core-error - E_CORE_ERROR - - - core-warning - E_CORE_WARNING - - - unknown - (any other) - - - -
+ + Debugger Protocol + + The debugger protocol is line-based. Each line has a + type, and several lines compose a + 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 + messages simultaneously. + + + A line has this format: + + +date time +host(pid) +type: +message-data + + + + + date + + + Date in ISO 8601 format + (yyyy-mm-dd) + + + + + time + + Time including microseconds: + hh:mm:uuuuuu + + + + + host + + + DNS name or IP address of the host where the script error was + generated. + + + + + pid + + + PID (process id) on host of the + process with the PHP script that generated this error. + + + + + type + + + Type of line. Tells the receiving program about what it + should treat the following data as: + + Debugger Line Types + + + + Name + Meaning + + + + + start + + Tells the receiving program that a debugger message + starts here. The contents of + data will be the type of error + message, listed below. + + + + message + The PHP error message. + + + location + + File name and line number where the error occured. The + first location line will always + contain the top-level location. + data will contain + file:line. + There will always be a location line + after message and after every + function. + + + + + frames Number of 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). + + + + + function + + Name of function where the error occured. Will be + repeated once for every level in the function call + stack. + + + + end + + Tells the receiving program that a debugger message ends + here. + + + + +
+ + + + + data + + Line data. + + + - - Example Debugger Message - + + Debugger Error Types + + + + Debugger + PHP Internal + + + + + warning + E_WARNING + + + error + E_ERROR + + + parse + E_PARSE + + + notice + E_NOTICE + + + core-error + E_CORE_ERROR + + + core-warning + E_CORE_WARNING + + + unknown + (any other) + + + +
+ + + Example Debugger Message + 1998-04-05 23:27:400966 lucifer.guardian.no(20481) start: notice 1998-04-05 23:27:400966 lucifer.guardian.no(20481) message: Uninitialized variable 1998-04-05 23:27:400966 lucifer.guardian.no(20481) location: (null):7 @@ -202,12 +233,12 @@ 1998-04-05 23:27:400966 lucifer.guardian.no(20481) function: display 1998-04-05 23:27:400966 lucifer.guardian.no(20481) location: /home/ssb/public_html/test.php3:10 1998-04-05 23:27:400966 lucifer.guardian.no(20481) end: notice - + + + + - - - - +