![]() 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 the plugins will be in separate processes that's not (yet!) being debugged. When you select Run in the debugger, only the main browser process will be debugged. Multi-process issuesĬhromium can be challenging to debug because of its multi-process architecture. ![]() It will be faster if you set up a local cache in a empty directory on your computer. In Visual Studio, this goes in Tools > Options under Debugging > Symbols. If you are debugging official Google Chrome release builds, use the symbol server: For more information, see logging and user data directory details. ![]() Release builds place the file in the top level of the user data Chromium app directory, which is OS-version-dependent. Debug builds place the chrome_debug.log file in the out\Debug directory. Chrome debug logĮnable Chrome debug logging to a file by passing -enable-logging -v=1 command-line flags at startup. Using the IDE, go to the Debugging tab of the properties of the chrome project, and set the Command Arguments. user-data-dir=c:\tmp\my_debug_profile (replace the path as necessary) If you are debugging Google Chrome branded builds, or use a Chromium build as your primary browser, the profiles can collide so you can’t run both at once, and your stable browser might see profile versions from the future (Google Chrome and Chromium use different profile directories by default so won't collide). It‘s a good idea to use a different profile for your debugging. You will want to do local builds when using a debugger. Goma (the internal Google distributed build) will not produce symbols so most debugging won't work (see discussion thread). Note that the path to the binary must use backslashes and must include the “.exe” suffix or Visual Studio will open and do nothing. This assumes you have Visual Studio installed and have devenv.exe on your path. ![]() **devenv **/debugexe out\Debug\chrome.exe To start debugging an executable from the command line: You don’t need to use the IDE to build in order to use the debugger: most developers use Ninja to build, and then open the IDE for debugging as necessary. Getting started You can use Visual Studio‘s built-in debugger or WinDBG to debug Chromium. First see get the code for checkout and build instructions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |