Remote Debugging Protocol: Difference between revisions

Jump to navigation Jump to search
m
→‎Pause Types: Clarify; fix grammar.
(Refined and expanded.)
m (→‎Pause Types: Clarify; fix grammar.)
Line 255: Line 255:
== Pause Types ==
== Pause Types ==


The <tt>pause-for</tt> property of a <tt>attach</tt> and <tt>resume</tt> packets specifies which kinds of events in the thread the client is interested in hearing about. The <i>pause-types</i> value is an object each of whose properties names a particular kind of pause, as appearing in the "type" field of a "paused" packet.
The <tt>pause-for</tt> property of a <tt>attach</tt> and <tt>resume</tt> packets specifies which kinds of events in the thread the client is interested in hearing about. The <i>pause-types</i> value is an object whose properties are named after pause reason types (<tt>pre-call</tt> or <tt>stepped</tt>, for example) and have the value <tt>true</tt> if such pauses are of interest to the client. The property names are the possible values of the "type" field of the <i>reason</i> in a "paused" packet.


For example, the following <i>resume</i> packet would instruct <i>thread</i> to continue until the current function call is about to return, or throw an exception:
For example, the following <i>resume</i> packet would instruct <i>thread</i> to continue until the current function call is about to return, or the thread is about to throw an exception:


   { "to":<i>thread</i>, "type":"resume", "pause-for": { "pre-call":true, "pre-throw":true } }
   { "to":<i>thread</i>, "type":"resume", "pause-for": { "pre-return":true, "pre-throw":true } }


Certain pause types cause other pause types to be included automatically:
Certain pause types cause other pause types to be included automatically, if those pause types are not mentioned explicitly:


{|
{|
!Pause type
!Pause type
!Also implies
!Also implies, if not mentioned explicitly
|-
|-
| <tt>pre-throw</tt>
| <tt>pre-throw</tt>
Confirmed users
496

edits

Navigation menu