There are two Visual Studio extensions that enable the debugger to automatically attach to all Chrome processes, so you can debug all of Chrome at once. You can also get the process IDs associated with each tab from the Chrome Task Manager (right-click on an empty area of the window title bar to open). The ProcessExplorer tool has a process tree view where you can see how these processes are related. The code that actually renders web pages (the Renderer) and th e plugins will be in separate processes that's not (yet!) being debugged. When you select Run in the debugger, only the main browser p rocess will be debugged. Having the correct version of the source files automatically show up saves significant time so you should definitely set this.Ĭhromium can be challenging to debug because of its multi-process architecture. This is highly recommended when debugging released Google Chrome builds or looking at crash dumps. srcfix in windbg, Tools-> Options-> Debugging-> General-> Enable source server support in Visual Studio) so that the correct source files will automatically be downloaded based on information in the downloaded symbols.Īdditionally, you must have python in your path in order for the command that fetches source files to succeed launching the debugger from the same environment as where you build Chromium is an easy way to ensure it's present. You should set up source indexing in your debugger (.
0 kommentar(er)
