Lines Matching full:debug

2 Duktape debug client and JSON debug proxy
9 target supporting the example TCP transport (``examples/debug-trans-socket``)
12 Also provides a JSON debug proxy with a JSON mapping for the Duktape debug
50     # that on the debug client.
67 Once the required packages are installed, the NodeJS debug client will be
72 The debug client automatically attaches to the debug target on startup.
73 If you start the debug target later, you'll need to click "Attach" in the
76 Using the JSON debug proxy
79 There are two JSON debug proxy implementations: one implemented in DukLuv
87 easy to embed in a custom debug client: you just include the DukLuv executable
88 and the JSON proxy source file in your debug client.
104   - ``.\build\Debug\dukluv.exe`` on Windows
144     Running Dukluv based debug proxy
147 …2016-02-17T13:59:42.325Z INF Proxy: Listening for incoming JSON debug connection on 0.0.0.0:9093, …
149     2016-02-17T13:59:47.994Z INF Proxy: Connecting to debug target at 127.0.0.1:9091
151     2016-02-17T13:59:47.994Z INF Proxy: Connected to debug target at 127.0.0.1:9091
194 A Node.js-based JSON debug proxy is also provided by ``duk_debug.js``::
196     # Same prerequisites as for running the debug client
230 A telnet connection allows you to experiment with debug commands by simply
231 copy-pasting debug commands to the telnet session.  This is useful even if
234 The debug target used by the proxy can be configured with ``duk_debug.js``
240 The NodeJS debug client needs to be able to find source code files matching
242 target and on the debug client must match exactly**, because e.g. breakpoints
260 and added a breakpoint, the breakpoint fileName sent to the debug target
273     | Web browser       |  [debug UI]
280     | duk_debug.js      |  [debug client]
287           |          ||---- [debug protocol stream]
288           |          ||     (between debug client and Duktape)
296     :     |          ||     :   [debug API]
297     :     +----------||-------- debug transport callbacks
306 The debug transport is application specific:
308 * Duktape command line ("duk") and this debug client use an **example** TCP
315 The debug protocol running inside the transport is transport independent:
317 * The debug protocol is documented in ``doc/debugger.rst``.
319 * This debug client provides further concrete examples and clarifications
327 custom transport both for the target device and for the debug client.
332 Implement the debug transport callbacks needed by ``duk_debugger_attach()``.
334 See ``doc/debugger.rst`` for details and ``examples/debug-trans-socket``
337 Debug client alternative 1: duk_debug.js + custom TCP proxy
348 This is a straightforward option and a proxy can be used with other debug
354 Debug client alternative 2: duk_debug.js + custom NodeJS stream
372 Debug client alternative 3: custom debug client
375 You can also implement your own debug client and debug UI with support for
382 The JSON debug proxy allows you to implement a debug client without needing
383 to implement the Duktape binary debug protocol.  The JSON protocol provides