Hi Peter

See answers inlined below:

On Sun, Aug 30, 2009 at 21:21, <[email protected]> wrote:

> Hi Soren
>
> Thank you for explanation. Let me withdraw my CL now.
>
> On the other hand I'm interested in developing support of V8 debugger
> because of chromedevtools project I'm working on.
>
> As I understand our main issue is multi-thread aspects
> V8<->some_debug_agent communication.
>
> Couple of Qs:
>
> 1. Can we have all debug commands "forced", which means that if V8 is
> running at the moment, it interrupts and process command.


 We already have this feature which can be enabled through the "debugger
auto break" flag. When this is enabled a special break flag (debug command
break) is set when a debugger JSON command enters the command queue. The
flag currently defaults to true, but in Chrome the devtools sets this to
true.


> 2. Provided #1 == true, "break" seems to be a regular JSON command. Do
> we need an out-of-order hi-pri "break" command in this case?  We
> probably only need it to interrupt other requests, notably "evaluate". I
> don't know it we really want to support this, but it looks nice.
>

When using the message based debugger API this will be true. Currently the
difference between the debug break flag and the debug command break flag is
that for the later JavaScript execution resumes afterwards. If the JSON
command was a break only command then execution should not continue.

For the event based API we still need the debug break command as a direct
API call.


>
> 3. Can we start adding API for embedder to run for us a spare cycle of
> V8 to process pending debug command? I'll try to submit a corresponding
> CL soon.
>

Is your suggesting a callback to the embedder when a debugger command has
entered the queue to give it a change to execute some JavaScript to give V8
a chance run, hit the debug command break and process the queue? It would
then be up to the embedder to schedule V8 to run something (e.g. "void 0")
on the correct thread.


> Peter
>
> http://codereview.chromium.org/160605
>

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to