RESOLVED FIXED37604
[V8] Web Inspector: implement ScriptDebugServer for v8 engine
https://bugs.webkit.org/show_bug.cgi?id=37604
Summary [V8] Web Inspector: implement ScriptDebugServer for v8 engine
Yury Semikhatsky
Reported 2010-04-14 13:54:50 PDT
We need to implement ScriptDebugServer for v8. This would allow to have common debugging protocol which wouldn't depend on the underlying JS engine.
Attachments
patch (48.24 KB, patch)
2010-04-15 06:37 PDT, Yury Semikhatsky
no flags
patch (48.43 KB, patch)
2010-04-15 07:06 PDT, Yury Semikhatsky
no flags
patch (48.43 KB, patch)
2010-04-15 07:15 PDT, Yury Semikhatsky
no flags
patch (48.51 KB, patch)
2010-04-15 08:15 PDT, Yury Semikhatsky
pfeldman: review-
patch (48.58 KB, patch)
2010-04-15 11:11 PDT, Yury Semikhatsky
pfeldman: review+
Yury Semikhatsky
Comment 1 2010-04-15 06:37:24 PDT
WebKit Review Bot
Comment 2 2010-04-15 06:38:14 PDT
Attachment 53431 [details] did not pass style-queue: Failed to run "WebKitTools/Scripts/check-webkit-style" exit_code: 1 Last 3072 characters of output: sorted. [build/include_order] [4] WebCore/bindings/v8/ScriptDebugServer.cpp:62: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:126: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:144: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:174: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:219: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:291: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:292: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:293: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:295: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:298: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:299: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:300: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:301: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:302: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:303: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:304: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:305: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.cpp:306: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/custom/V8InjectedScriptHostCustom.cpp:161: Tab found; better to use spaces [whitespace/tab] [1] WebKit/chromium/src/js/DebuggerScript.js:182: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:183: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:184: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:185: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:186: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:187: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/src/js/DebuggerScript.js:188: Line contains tab character. [whitespace/tab] [5] WebCore/bindings/v8/ScriptDebugServer.h:134: Tab found; better to use spaces [whitespace/tab] [1] WebCore/bindings/v8/ScriptDebugServer.h:135: Tab found; better to use spaces [whitespace/tab] [1] WebKit/chromium/ChangeLog:5: Line contains tab character. [whitespace/tab] [5] WebKit/chromium/ChangeLog:6: Line contains tab character. [whitespace/tab] [5] Total errors found: 34 in 19 files If any of these errors are false positives, please file a bug against check-webkit-style.
Eric Seidel (no email)
Comment 3 2010-04-15 06:39:53 PDT
Early Warning System Bot
Comment 4 2010-04-15 06:42:04 PDT
WebKit Review Bot
Comment 5 2010-04-15 06:57:57 PDT
Yury Semikhatsky
Comment 6 2010-04-15 07:06:54 PDT
Created attachment 53434 [details] patch Fixed errors found by try bots.
WebKit Review Bot
Comment 7 2010-04-15 07:09:34 PDT
Attachment 53434 [details] did not pass style-queue: Failed to run "WebKitTools/Scripts/check-webkit-style" exit_code: 1 WebCore/ChangeLog:4: Line contains tab character. [whitespace/tab] [5] Total errors found: 1 in 19 files If any of these errors are false positives, please file a bug against check-webkit-style.
WebKit Review Bot
Comment 8 2010-04-15 07:13:56 PDT
Yury Semikhatsky
Comment 9 2010-04-15 07:15:04 PDT
Created attachment 53435 [details] patch Removed tab from WebCore/ChangeLog
WebKit Review Bot
Comment 10 2010-04-15 07:21:18 PDT
Pavel Feldman
Comment 11 2010-04-15 07:25:13 PDT
Comment on attachment 53434 [details] patch Looks good except for "if (jsEngine === "v8")" in InjectedScript.
Yury Semikhatsky
Comment 12 2010-04-15 08:15:08 PDT
Created attachment 53439 [details] patch Fixed Chromium compilation issue related to StringHash.h import
Pavel Feldman
Comment 13 2010-04-15 10:53:15 PDT
Comment on attachment 53439 [details] patch Please explain the InjectedScript fork and the way you are going to resolve it asap (as we discussed offline) in the FIXME. Otherwise looks good.
Yury Semikhatsky
Comment 14 2010-04-15 11:11:06 PDT
Created attachment 53453 [details] patch Filed a bug(https://bugs.webkit.org/show_bug.cgi?id=37663) and added FIXME comment with regard to call stack iteration.
Yury Semikhatsky
Comment 15 2010-04-15 11:42:02 PDT
Committed r57660
Albert J. Wong
Comment 16 2010-04-15 13:45:42 PDT
Reverted r57660 for reason: Broke a large number of inspector layout tests in chromium. Committed r57670: <http://trac.webkit.org/changeset/57670>
Yury Semikhatsky
Comment 17 2010-04-15 18:10:51 PDT
Committed exactly same patch r57701. The Chromium test failure was related to gyp dependency tracking(see http://code.google.com/p/chromium/issues/detail?id=29695).
Note You need to log in before you can comment on or make changes to this bug.