Confirmed users
497
edits
(Bring up to date; restructure. More to come.) |
No edit summary |
||
Line 29: | Line 29: | ||
js::dbg2 dispatch facilities simply return, and the code that generated the | js::dbg2 dispatch facilities simply return, and the code that generated the | ||
event resumes execution. | event resumes execution. | ||
If the debugger elects to debug a worker thread, the main thread acts as a | |||
proxy, relaying messages to the worker thread's server: | |||
[[File:worker-thread-event.png]] | |||
(I am not sure whether we want to keep things this way, or have the | |||
debugger connect directly to its debuggees. Being able to debug many | |||
threads with a single socket connection seems like a win, and we still get | |||
the inter-thread synchronization benefits; but latency might affect the | |||
debuggers' users' experience. Let's code it and see!) | |||
== Evaluating User Expressions == | == Evaluating User Expressions == |