28 | | |
29 | | = Debugging DumpRenderTree = |
30 | | |
31 | | 1. Set `DumpRenderTree` as your startup project. |
32 | | |
33 | | 2. Configure the arguments and environment variables for the test runner. |
34 | | |
35 | | In the DumpRenderTree project in the Solution Explorer window, right-click and select `Properties...`. |
36 | | * In the `Command Arguments` section, enter the absolute paths for the tests you want to run, separated by spaces. |
37 | | * In the `Environment` section, put `PATH=$(ProgramFiles)\Common Files\Apple\Apple Application Support;$(PATH)` |
38 | | |
39 | | Click OK to close the Project Properties window. |
40 | | |
41 | | 3. Launch the debugger. |
42 | | |
43 | | Right-click on the DumpRenderTree project, and choose `Debug > Start New Instance`. |
44 | | |
45 | | = Debugging WebKit2 = |
46 | | |
47 | | (AppleWin removed WebKit2 support.) |
48 | | (Ed. note: These instructions were written for VS2005 and are likely outdated) |
49 | | |
50 | | 1. Make sure the '''Use WebKit2 for New Tabs''' option is enabled in Safari’s '''Debug''' menu |
51 | | 2. Right after you tell Visual Studio to Run the version of Safari that you just built, hold down the Shift-Control-Alt keys |
52 | | 3. A dialog should pop up to notify that you can now attach a debugger to the `WebProcess` — ''(Do not click OK yet!)'' |
53 | | 4. In Visual Studio select '''Attach to Process…''' in the '''Debug''' Menu. |
54 | | 5. In the window that comes up, select the `WebKit2WebProcess` with the title "WebKit2WebProcess has launched", and Attach |
55 | | 6. Go back to the dialog from Step 3 and click '''OK''' |
56 | | |
57 | | |
58 | | You’re now debugging both the `UIProcess` and the `WebProcess`. Your breakpoints in either should work accordingly. |
59 | | |
60 | | Alternatively, you can add a VS Toolbar Item to attach to the `WebProcess`. |