projects / platform / upstream / v8.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 50cc3a5) | patch
Do not unnecessarily expose execution state in debug event data.
authoryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Jun 2014 09:13:09 +0000 (09:13 +0000)
committeryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Jun 2014 09:13:09 +0000 (09:13 +0000)
commit3247a71c787b19c9901a25073b7afb76ee63f4c8
tree4bc9e441cd4c153fb72cea78871a6ee220d41012tree | snapshot
parent50cc3a5ba8059ceb0280bf4f0e159cfde15df440commit | diff
Do not unnecessarily expose execution state in debug event data.

When we fire a debug event, we create duplicate execution state objects,
one as argument for the debug event listener, one as property on the
debug event data object. The latter is never used by chrome.

R=yurys@chromium.org

Review URL: https://codereview.chromium.org/355793002

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22001 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/debug-debugger.js diff | blob | history
src/debug.cc diff | blob | history
test/mjsunit/mjsunit-assertoptimized.js [deleted file] blob | history
test/mjsunit/mjsunit.status diff | blob | history
Domain: Web Framework / Web Engine;