Windbg Symbol Path Download For Mac
This document explains how to debug Mozilla-derived applications such as Firefox, Thunderbird, and SeaMonkey on macOS using Xcode. If you want to debug from the terminal see. Battle.net has an unlisted overwatch setup for mac. For specific information on a way to debug hangs, see.
Creating a debuggable build First, you need to build the application you're going to debug using -disable-optimize -enable-debug-symbols in your.mozconfig (also add -enable-debug if you want assertions etc. Compiled in).
See if you need help creating your own build. Creating an Xcode project. If you try to create a new Xcode project in an existing directory then Xcode will delete its existing contents (Xcode will warn you beforehand). To work around that the steps below will have you initialize the project outside the Mozilla source tree, close the project, copy the.xcodeproj project 'file' into the source tree, and only then will you reopen the project to finish setting it up. Note also that since Xcode 7.3.1 it doesn't seem to be possible to have the Xcode project live outside the source tree. If you try to do that then Xcode will simply copy the source files under the project directory rather than link to them (still the case in Xcode 10?) which breaks debugging and the possibility to modify-rebuild-relaunch from inside Xcode. These steps were last updated for Xcode 10:.
Open Xcode, and create a new Project with File New Project. Select the 'Cross-platform' tab then under the 'Other' template group select the 'Empty' project type. The click Next. Name the project and click Next. Select a temporary directory to create the project files in and then click Create. Before going any further, close the project (File Close Project) and open Finder.
Find the.xcodejproj directory in the temporary directory, move it into your Mozilla source tree, and then double-click on it to open it. In the left-hand pane in Xcode you should see a tree where the root item has the project name, and under it is the temporary directory that you originally created the Xcode project in under. Right click on the temporary directory and delete it, then right click on the root item and select 'Add files to ', select the contents of your source directory, and click Add. In the Product menu, select Scheme New Scheme and name your scheme (for example, 'Debug'). After you click OK, Xcode should open the settings window for the new scheme. (If not, then open its settings from the Product Edit Scheme menu.). Select 'Run' on the left-hand side of the settings window, then select the 'Info' tab.
Windbg Symbol Path Download For Mac
Set the Executable by clicking on 'None' and selecting 'Other.' A new dialog titled 'Choose an executable to launch' will pop up. Browse to the.app file that you want to debug ( Firefox.app, Nightly Debug.app etc). The.app file is typically found inside the dist folder in your build directory. If you are debugging Firefox, Thunderbird, or some other application that supports multiple profiles, using a separate profile for debugging purposes is recommended. See 'Having a profile for debugging purposes' below. Select the 'Arguments' tab in the scheme editor, and click the '+' below the 'Arguments passed on launch' field.
Add '-P profilename', where profilename is the name of a profile you created previously. Repeat that to also add the argument '-no-remote'. Also in the 'Arguments' panel, you may want to add an environment variable MOZDEBUGCHILDPROCESS set to the value 1 to help with debugging e10s. Select 'Build' from the left of the scheme editor window, and check that there is nothing listed under Targets (otherwise it may cause problems when you try to run the executable for debugging since you will get build errors). Click 'Close' to close the scheme editor. At this point you can run the application from Xcode, and when you pause or hit breakpoints it should show open the correct source file at the correct line. Setting up lldb lldb is the debugger XCode version 5 and above uses under the hood (previous versions used gdb).
The file in the source tree imports many useful but when debugging in XCode this file is not loaded by default since Xcode does not run using $topsrcdir as its current working directory (see ). To work around this add the following to $HOME/.lldbinit and set fallbacktopsrcdir to a Mozilla source directory that you regularly update: # Import Mozilla settings and utilities (the awkward structure of these # commands is necessary to avoid double importing of the Mozilla.lldbinit): script fallbacktopsrcdir = script istopsrcdir = os.path.exists('mozilla-config.h.in') script topsrcdir = os.getcwd if istopsrcdir else fallbacktopsrcdir script ignored = istopsrcdir or lldb.debugger.HandleCommand('command source -s true ' + os.path.join(topsrcdir, '.lldbinit')) see for more information.
You will need to use Python v2.x supplied by macOS, otherwise, you will encounter this error: ImportError: cannot import name removedeadweakref. Run the following to correct this: brew unlink python@2. Having a profile for debugging purposes It is recommended to create a separate profile to debug with, whatever your task, so that you don't lose precious data like Bookmarks, saved passwords, etc.
So that you're not bothered with the profile manager every time you start to debug, expand the 'Executables' branch of the 'Groups & Files' list and double click on the Executable you added for Mozilla. Click the plus icon under the 'Arguments' list and type '-P ' (e.g. '-P MozillaDebug').
Close the window when you're done. Running a debug session Make sure breakpoints are active (which implies running under the debugger) by opening the Product menu and selecting 'Debug / Activate Breakpoints' (also shown by the 'Breakpoints' button in the top right section of the main window). Then click the 'Run' button or select 'Run' from the Product menu.
Setting breakpoints Setting a breakpoint is easy. Just open the source file you want to debug in Xcode, and click in the margin to the left of the line of code where you want to break. During the debugging session, each time that line is executed, the debugger will break there, and you will be able to debug it. Note that with the default configuration, some breakpoints will be listed as 'pending', and XCode will not stop at them. If you don't include the Mozilla's.lldbinit, you must at least put settings set target.inline-breakpoint-strategy always in your $HOME/.lldbinit as recommended on. Using Mozilla-specific lldb commands If you included the.lldbinit when, you can use Mozilla-specific lldb commands in the console, located in the Debug area of XCode. For example, type js to see the JavaScript stack.
For more information, see. Debugging e10s child processes Using XCode to debug child processes created by an e10s-enabled browser is a little trickier than debugging a single-process browser, but it can be done. These directions were written using XCode 6.3.1. Complete all the steps above under 'Creating the Project'. From the 'Product' menu, ensure the scheme you created is selected under 'Scheme', then choose 'Scheme Edit Scheme'. In the resulting popup, click 'Duplicate Scheme'.
Give the resulting scheme a more descriptive name than 'Copy of Scheme'. Select 'Run' on the left-hand side of the settings window, then select the 'Info' tab. Set the Executable by clicking on the 'Executable' drop-down, and selecting the plugin-container.app that is inside the app bundle of the copy of Firefox you want to debug. On the same tab, under 'Launch' select 'Wait for executable to be launched'. On the 'Arguments' tab, remove all arguments passed on launch. Now you're ready to start debugging:. From the 'Product' menu, ensure the scheme you created above is selected under 'Scheme'.
Click the 'Run' button. The information area at the top of the window will show 'Waiting for plugin-container to launch'. From a command line, run your build of Firefox. When that launches a child process (for example, when you start to load a webpage), XCode will notice and attach to that child process.
You can then debug the child process like you would any other process. When you are done debugging, click the 'Stop' button and quit the instance of Firefox that you were debugging in the normal way. For some help on using lldb see.
Other resources Apple has an extensive list of. Try asking in our IRC channels.