Hi Aaron, Great work getting this landed, and thanks for doing the work to minimize the impact on everyone!
On Thu, Sep 27, 2018, at 11:19 AM, Aaron Klotz wrote: > 2. Debugging the browser process > -------------------------------- > > If you launch Firefox via a debugger, the initial process will now be > the launcher process instead of the browser process. To debug the > browser process, here are your options: > > * You can attach your debugger to the browser process once it has > started. Obviously this solution is less than ideal if you want to debug > something during startup; We have `MOZ_DEBUG_CHILD_PROCESS` for e10s content processes[1]. Would something similar (or maybe just supporting that?) be useful for the browser process as well? > * If you use WinDbg, you may start your debugging session from the > command line with the "-o" option to ensure that the debugger attaches > to all child processes. If you prefer opening your executable via the > GUI, you may select the "Debug child processes also" checkbox within the > "Open Executable" file picker. > * If you use Visual Studio, you may install the Child Process Debugging > Power Tool [3] which, once configured, will make the VS debugger > automagically attach to the launcher's child processes. Can we make these work automatically via mozdebug so that `mach run --debug` works directly? -Ted 1. https://mikeconley.ca/blog/2014/04/25/electrolysis-debugging-child-processes-of-content-for-make-benefit-glorious-browser-of-firefox/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
