зеркало из https://github.com/mozilla/gecko-dev.git
3f9e98f591
We always used to pause when "attaching" the thread actor. We ought to call ThreadActor's attach method first before using it. And this method do various things: * Initialize the Debugger API, enable it, register various listeners, so that breakpoint can work, * Pause the current thread by starting a nested event loop So that we also ought to resume the thread, by calling ThreadActor's resume right after attach. Otherwise the page would be paused as soon as we open the DevTools. Which sounds like something we might have wanted a very long time ago. But sounds like pure legacy behavior from today's perspective. Differential Revision: https://phabricator.services.mozilla.com/D99919 |
||
|---|---|---|
| .. | ||
| dns-packet | ||
| example | ||
| moz-http2 | ||
| node-http2 | ||
| node-ip | ||
| README | ||
| dbg-actors.js | ||
| head.js | ||
| mach_commands.py | ||
| mach_test_package_commands.py | ||
| moz.build | ||
| remotexpcshelltests.py | ||
| runxpcshelltests.py | ||
| selftest.py | ||
| xpcshellcommandline.py | ||
README
Simple xpcshell-based test harness converted from netwerk/test/unit Some documentation at http://developer.mozilla.org/en/docs/Writing_xpcshell-based_unit_tests See also http://wiki.mozilla.org/SoftwareTesting:Tools:Simple_xpcshell_test_harness