I know that most people aren't debugging e10s on Windows, but if you
are, here's a protip (provided that you are using WinDbg):
If you include the "-o" option in the debugger args, WinDbg will
automatically attach itself to all child processes that are started by
the chrome process. No special environment variables or process startup
sleeps required.
-Aaron
On 3/24/2016 10:51 AM, Boris Zbarsky wrote:
On 3/24/16 12:43 PM, Andrew Halberstadt wrote:
I'm not aware of work around this. If --debugger is completely busted
with e10s, I could potentially make --debugger imply --disable-e10s
until it gets fixed. Is there a bug on file?
I don't know of one.
It's not that it's busted per se, it's that it attaches the debugger
to the parent process. Which is not very helpful, in most cases.
What would be ideal (at least on unixy systems) is if we managed to
detect the child process starting and popped up an instance of $TERM
or so, with a debugger running in it and attached to the child.
I also forgot to mention that command defaults are likely coming soon,
so once bug 1255450 lands you'll be able to make a .machrc with:
[defaults]
mochitest = --disable-e10s
Ah, nice. Still, I agree it would be good to be testing e10s if we
can make the debugging experience there better.
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
