commit 777c3353d892b7b093be379c21df6cb39e5adc5a
parent ed0af44645631521c59aa5b5bbe2c8f469c97bff
Author: Yannis Juglaret <yjuglaret@mozilla.com>
Date: Tue, 9 Dec 2025 08:47:40 +0000
Bug 1943427 - Update link to Visual Studio multiprocess extension in our docs. r=win-reviewers,gstoll DONTBUILD
Differential Revision: https://phabricator.services.mozilla.com/D275444
Diffstat:
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/docs/contributing/debugging/debugging_on_windows.rst b/docs/contributing/debugging/debugging_on_windows.rst
@@ -17,12 +17,17 @@ and even in non-e10s mode, does not start the main process directly, it
starts it via a Launcher Process. This means that Visual Studio will
only attach to the first process it finds, and will not hit any
break-point (and even notifies you that it cannot find their location).
-`Microsoft Child Process Debugging Power
-Tool <https://marketplace.visualstudio.com/items?itemName=vsdbgplat.MicrosoftChildProcessDebuggingPowerTool>`__
+
+For Visual Studio 2022 and above,
+`Microsoft Child Process Debugging Power Tool 2022+
+<https://marketplace.visualstudio.com/items?itemName=vsdbgplat.MicrosoftChildProcessDebuggingPowerTool2022>`__
allows automatically attaching to child processes, such as Web Content
process, GPU process, etc. Enable it by going its configuration menu in
"Debug > Other debugging targets > Child process debugging settings",
-and ticking the box.
+and ticking the box. The same extension exists for older versions of Visual
+Studio as
+`Microsoft Child Process Debugging Power Tool
+<https://marketplace.visualstudio.com/items?itemName=vsdbgplat.MicrosoftChildProcessDebuggingPowerTool>`__.
If you have followed the steps in :ref:`Building Firefox for
Windows <Building Firefox On Windows>`
