Bug 66596
| Summary: | Update Debugging WebKit instructions for debugging with Safari 5.1/WebKit 2 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Bates <dbates> |
| Component: | WebKit Website | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Major | CC: | ap, arv, burg, mjs |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 67101, 67102 | ||
| Bug Blocks: | |||
Daniel Bates
Safari 5.1 shipped with WebKit 2. We should update the Debugging WebKit page <http://www.webkit.org/building/debug.html> to describe how to support debugging WebKit 2.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Erik Arvidsson
Here is how to do it for people that do not know yet:
defaults write com.apple.Safari IncludeInternalDebugMenu 1
And then in Safari 5.1 you'll see a Debug menu. From here you can either do "New Single-process Window" or turn off "Use Multi-process Windows". Once that is done your Xcode breakpoints will be hit.
Maciej Stachowiak
The better way to do it is here:
https://trac.webkit.org/wiki/Debugging%20the%20WebKit2%20Web%20Process
Brian Burg
The linked wiki page is empty and the content appears to be on debug.html now. Closing bug.