For the Servo debugger, we need some kind of IPC layer:
The debugger server (i.e. the thing that talks the Chrome debugging
protocol) needs to live in the same process (and perhaps even the same
thread) as the constellation; it needs to work closely with the
constellation to figure out which scrip
.
>
> So whichever tool you use for this, please make sure that the API
> encourages the correct behavior.
>
> Cheers,
> David
>
> On 16/11/16 14:16, Eddy Bruel wrote:
> > For the Servo debugger, now that we've begun landing the Rust interface
> to
> > t
For the Servo debugger, now that we've begun landing the Rust interface to
the Debugger API, we can also started working on the next step, which is an
IPC client/server on top of that Rust interface. This IPC server will allow
the main debugger server, which lives in a separate process, to talk to
Hello!
I am sure most of you are already aware of this, but for those of you who
are not: the devtools team is taking its first steps towards implementing a
JS debugger for Servo!
As part of this process, we started working on a Rust interface for the
SpiderMonkey debugger API a couple of weeks a
-- Forwarded message --
From: Eddy Bruel
Date: Mon, Sep 19, 2016 at 5:45 PM
Subject: Maintaining a list of debugging targets in the debugger.
To: Jim Blandy , se...@mozilla.com
Cc: Patrick Brosset
Over the past few days, I've tried to come up with a way to maintain a li
As I mentioned in my previous post, I am trying to use the rust-websocket
library to implement a prototype debugger server for Servo.
The main server thread needs to wait for one of the following events:
1. An incoming WebSocket connection.
2. A message from the browser
Unfortunately, the former
I am currently writing a prototype of a debugger server for Servo that
works with the Chrome Debugging Protocol:
https://github.com/ejpbruel/servo/tree/acceptor
The Chrome Debugging Protocol works by first sending a HTTP request to
http://localhost:/json (where is the remote debugging
port). This
As I’m sure you are aware, the devtools team is taking the first steps
towards building a JS debugger for Servo.
One of the first questions one needs to answer when building a JS debugger
is: what should happen when the debugger is paused? In Gecko, we have a
separate debugger for each tab, so the
8 matches
Mail list logo