--- a/DebugClients/Python2/DebugClientBase.py Sat Sep 03 18:24:50 2016 +0200
+++ b/DebugClients/Python2/DebugClientBase.py Sat Sep 03 18:42:02 2016 +0200
@@ -149,27 +149,11 @@
Class implementing the client side of the debugger.
It provides access to the Python interpeter from a debugger running in
- another process whether or not the Qt event loop is running.
-
- The protocol between the debugger and the client assumes that there will be
- a single source of debugger commands and a single source of Python
- statements. Commands and statement are always exactly one line and may be
- interspersed.
-
- The protocol is as follows. First the client opens a connection to the
- debugger and then sends a series of one line commands. A command is either
- >Load<, >Step<, >StepInto<, ... or a Python statement.
- See DebugProtocol.py for a listing of valid protocol tokens.
-
- A Python statement consists of the statement to execute, followed (in a
- separate line) by >OK?<. If the statement was incomplete then the
- response is >Continue<. If there was an exception then the response
- is >Exception<. Otherwise the response is >OK<. The reason
- for the >OK?< part is to provide a sentinal (ie. the responding
- >OK<) after any possible output as a result of executing the command.
-
- The client may send any other lines at any other time which should be
- interpreted as program output.
+ another process.
+
+ The protocol between the debugger and the client is based on JSONRPC 2.0
+ PDUs. Each one is sent on a single line, i.e. commands or responses are
+ separated by a linefeed character.
If the debugger closes the session there is no response from the client.
The client may close the session at any time as a result of the script
@@ -217,7 +201,6 @@
self._fncache = {}
self.dircache = []
- self.mainProcStr = None # used for the passive mode
self.passive = False # used to indicate the passive mode
self.running = None
self.test = None
