Jonathan.Fischoff at am.sony.com
Tue Mar 9 15:23:11 PST 2010
Thanks for the links and explanation. I am still incredibly new to the codebase, but it looks like you have done much of what I need.
I wonder if coupling the debugging helper classes for JSC with WebCore is ideal. It appears that ScriptDebugServer could be separated into portions that do not require WebCore, that would facilitate the building of a debugger for just JSC.
Since you are on the precipice of forming a consensus, it might be worth designing the remoting so it could be used at a lower level.
From: jamey.hicks at nokia.com [mailto:jamey.hicks at nokia.com]
Sent: Tuesday, March 09, 2010 5:31 AM
To: Fischoff, Jonathan
Cc: webkit-dev at lists.webkit.org
I've been working on remote debugging/profiling of webkit and I've been leveraging work that the webkit and chromium guys did to separate the Web Inspector frontend from backend.
I was actually thinking about sending email to the list this morning about agreeing on a remote/on-device protocol for debugging and profiling webkit.
I have made two prototypes enable remote debugging. In these two prototypes, I have used the Web Inspector UI running in Safari or WebKit on a desktop connected to the backend running in a webkit instance on another device. My first prototype was all implemented in C++ for qtwebkit. There is a patch with this code:
Qt debug agent partially implementing ChromeDevTools and V8 debug protocol<https://bugs.webkit.org/attachment.cgi?id=48913> attached to https://bugs.webkit.org/show_bug.cgi?id=35016
On Mar 8, 2010, at 7:18 PM, ext Fischoff, Jonathan wrote:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev