[xdebug-dev] dbgp dbgp/debugger_protocol.txt - Fixed a little inconsistency in the DBGp specs.

Date: Fri Oct 22 20:11:08 CEST 2004
User: Derick Rethans
Directory: dbgp

Log Message:
[0.05]
- Fixed a little inconsistency in the DBGp specs.

Modified files:
           dbgp/debugger_protocol.txt (version: 1.2)

[FILE: /dbgp/debugger_protocol.txt]

===================================================================
RCS file: cvstemp,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- dbgp/debugger_protocol.txt:1.1.1.1 Fri Oct 22 15:57:20 2004 GMT
+++ dbgp/debugger_protocol.txt Fri Oct 22 16:11:08 2004 GMT
@@ -124,34 +124,34 @@
 
 Attributes in the init element can include:
     
- =============== ========================================================
- Attribute Description
- =============== ========================================================
- appid defined by the debugger engine
- idekey defined by the user. The DBGP_IDEKEY environment
- variable SHOULD be used if it is available,
- otherwise setting this value is debugger engine
- implementation specific. This value may be empty.
- session If the environment variable DBGP_COOKIE exists,
- then the init packet MUST contain a session
- attribute with the value of the variable. This
- allows an IDE to execute a debugger engine, and
- maintain some state information between the
- execution and the protocol connection. This value
- should not be expected to be set in 'remote'
- debugging situations where the IDE is not in
- control of the process.
- thread_id the systems thread id
- parent_appid the appid of the application that spawned the
- process. When an application is executed, it
- should set it's APPID into the environment.
- If an APPID already exists, it should first
- read that value and use it as the PARENT_APPID.
- language_name debugger engine specific, must not contain
- additional information, such as version, etc.
- protocol The highest version of this protocol supported
- fileuri URI of the script file being debugged
- =============== ========================================================
+ ================ ========================================================
+ Attribute Description
+ ================ ========================================================
+ appid defined by the debugger engine
+ idekey defined by the user. The DBGP_IDEKEY environment
+ variable SHOULD be used if it is available,
+ otherwise setting this value is debugger engine
+ implementation specific. This value may be empty.
+ session If the environment variable DBGP_COOKIE exists,
+ then the init packet MUST contain a session
+ attribute with the value of the variable. This
+ allows an IDE to execute a debugger engine, and
+ maintain some state information between the
+ execution and the protocol connection. This value
+ should not be expected to be set in 'remote'
+ debugging situations where the IDE is not in
+ control of the process.
+ thread the systems thread id
+ parent the appid of the application that spawned the
+ process. When an application is executed, it
+ should set it's APPID into the environment.
+ If an APPID already exists, it should first
+ read that value and use it as the PARENT_APPID.
+ language debugger engine specific, must not contain
+ additional information, such as version, etc.
+ protocol_version The highest version of this protocol supported
+ fileuri URI of the script file being debugged
+ ================ ========================================================
 
 The IDE responds by dropping socket connection, or starting with
 debugger commands.
Received on Fri Oct 22 2004 - 20:11:13 BST