Changeset 116320 in webkit
- Timestamp:
- May 7, 2012 10:42:07 AM (12 years ago)
- Location:
- trunk/Websites/webkit.org
- Files:
-
- 3 edited
-
ChangeLog (modified) (1 diff)
-
building/debug.html (modified) (1 diff)
-
building/tools.html (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/Websites/webkit.org/ChangeLog
r114982 r116320 1 2012-05-07 Dan Bernstein <mitz@apple.com> 2 3 webkit.org instructions for debugging WebProcess are unnecessarily complex 4 https://bugs.webkit.org/show_bug.cgi?id=85756 5 6 Reviewed by Darin Adler. 7 8 * building/debug.html: Added instructions for setting up and using the WebKit workspace for 9 debugging the Web process, as well as instructions for debugging the Web process from the 10 command line using debug-safari and debug-minibrowser. 11 * building/tools.html: Updated links and tweaked the language. 12 1 13 2012-04-23 Daniel Bates <dbates@webkit.org> 2 14 -
trunk/Websites/webkit.org/building/debug.html
r114978 r116320 6 6 <div class="mac-instructions"> 7 7 <h2>Debugging on Mac OS X</h2> 8 <p> Each WebKit component -- JavaScriptCore, WebCore, and WebKit2 -- contains its own Xcode project that depends on the build location specified in the project itself. In Xcode 4.3.2, choose Xcode > Preferences > Locations, click Locations, click the Advanced button, and ensure that the build location is Legacy.</p>8 <p>To debug from within Xcode, you can use the WebKit workspace. Ensure that the Products and Intermediates locations for the workspace match those used by <code>build-webkit</code> by choosing File > Workspace Settings and clicking the Advanced button, selecting Custom, Relative to Workspace, and entering WebKitBuild both for Products and for Intermediates. Note that if you have specified a custom build location in Xcode preferences, then you don’t need to do this.</p> 9 9 <h3>Debugging UIProcess</h3> 10 10 <p>Follow the instructions on the <a href="debug-mac-uiprocess.html">debugging UIProcess</a> page.</p> 11 11 <h3>Debugging WebProcess</h3> 12 <ol> 13 <li><p>Launch Safari</p> 14 <p>Follow the instructions on <a href="run.html">Running WebKit</a> to launch Safari from the command line with the WebKit version you built. Alternatively you can <a href="debug-mac-uiprocess.html">use the WebKit2 Xcode project to launch Safari</a>.</p> 15 </li> 16 <li><p>Open a project</p> 17 <p>Open the Xcode project belonging to the component -- WebCore or JavaScriptCore -- you want to debug.</p> 18 </li> 19 <li><p>Attach to WebProcess</p> 20 <p>Choose Product > Attach to Process > WebProcess.</p> 21 </li> 22 <li><p>See the <a href="https://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/Debugging/Debugging.html#//apple_ref/doc/uid/TP40010215-CH3-SW1">Xcode Debugging Guide</a> for more information on using Xcode to debug software on Mac OS X.</p> 23 </li> 24 </ol> 12 <ul> 13 <li> 14 <p>From the command line:</p> 15 <p>Execute the <code>debug-safari</code> or <code>debug-minibrowser</code> <a href="/coding/scripts.html">script</a> with the <code>--target-web-process</code> option. It will start the debugger with WebProcess as the target and with command-line arguments that will make WebProcess run Safari or MiniBrowser as its client. At the debugger prompt, enter <code>run</code> to start the process.</p> 16 </li> 17 <li> 18 <p>From Xcode:</p> 19 <p>Open the WebKit workspace and choose “All Source (target WebProcess)” from the Scheme pop-up menu in the toolbar, then choose Product > Run. If WebKit is already built, it is quicker to choose Product > Perform Action > Run Without Building</p> 20 </li> 21 </ul> 25 22 </div> 26 23 <div class="windows-instructions"> -
trunk/Websites/webkit.org/building/tools.html
r114982 r116320 7 7 <h4>Mac OS X</h4> 8 8 <ol> 9 <li><p>Install the Xcode Tools package</p>10 <p> Install the Xcode Tools package from <a target="installtools" href="http://connect.apple.com/">http://connect.apple.com</a>. Xcode 3.1.4 or later is required to build.</p>9 <li><p>Install Xcode</p> 10 <p>Get Xcode from <a target="installtools" href="https://developer.apple.com/downloads">https://developer.apple.com/downloads</a>. Xcode 3.1.4 or later is required to build.</p> 11 11 <li><p>Install the Xcode Command Line Tools (located under Xcode Preferences > Downloads)</p> 12 12 <p><b>Note:</b> Before you can use the Xcode 4.3.2 tools, you must either run <code>sudo xcode-select -switch /Applications/Xcode.app</code> or 13 set the environment variable DEVELOPER_DIR to <code>/Applications/Xcode.app/Contents/Developer</code>. See < code>man xcode-select</code> for more details.</p>14 <p><b>Note:</b> This step is not required for versions of Xcode older than 4.3.</p>13 set the environment variable DEVELOPER_DIR to <code>/Applications/Xcode.app/Contents/Developer</code>. See <a href="x-man-page://xcode-select">the <code>xcode-select</code> man page</a> for more details.</p> 14 <p><b>Note:</b> This step is not required for versions of Xcode earlier than 4.3.</p> 15 15 <li><p>Install Java for Mac OS X Developer Package</p> 16 <p>Download and install the latest OS-appropriate "Java for Mac OS X Developer Package" from <a href="http://connect.apple.com/">http://connect.apple.com/</a> (located under Downloads > Java).</p>16 <p>Download and install the latest OS-appropriate “Java for Mac OS X Developer Package” from <a target="installtools" href="https://developer.apple.com/downloads">https://developer.apple.com/downloads</a>.</p> 17 17 </ol> 18 18 </div>
Note: See TracChangeset
for help on using the changeset viewer.
