fune/devtools/server
Alexandre Poirot 5cb1635d84 Bug 1803616 - [devtools] Implement a Javascript Tracer in the debugger. r=devtools-reviewers,devtools-backward-compat-reviewers,nchevobbe
On the server side, this patch introduces:
* a new "tracer" Target Scope actor to start and stop tracing per target
* a new TRACING_STATE resource in order to report to the client when we start/stop tracing and with which log method.

On the frontend side, this patch introduces:
* a global tracer button, which will enable/disable tracing for all targets/threads
  all at once.
* a global header, similar to pause, reporting if any target is tracing or not.
The header reuses the pause header and we may want to followup to better coordinate case
where we pause and trace at the same time. Only one of the two states is displayed.

We may want to followup here to be able to trace only one target and see the state per target.

Differential Revision: https://phabricator.services.mozilla.com/D163614
2023-03-14 17:17:05 +00:00
..
actors Bug 1803616 - [devtools] Implement a Javascript Tracer in the debugger. r=devtools-reviewers,devtools-backward-compat-reviewers,nchevobbe 2023-03-14 17:17:05 +00:00
connectors Bug 1766485 - [devtools] Consider server side target switching always enabled for tab toolboxes. r=devtools-reviewers,nchevobbe 2023-01-30 12:49:54 +00:00
performance
socket
startup Bug 1578975 - [devtools] Remove now-unused setupInParent code. r=devtools-reviewers,jdescottes 2023-01-29 20:50:48 +00:00
tests Bug 1805288 - Part 2: Use ChromeUtils.defineLazyGetter from XPCOMUtils.defineLazyGetter. r=smaug,devtools-reviewers,ochameau 2023-03-08 07:11:02 +00:00
devtools-server-connection.js Bug 1578975 - [devtools] Remove now-unused setupInParent code. r=devtools-reviewers,jdescottes 2023-01-29 20:50:48 +00:00
devtools-server.js
moz.build