yangguo@chromium.org 3247a71c78 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		2014-06-25 09:13:09 +00:00
..
benchmarks	Merge experimental/a64 to bleeding_edge.	2014-02-12 09:19:30 +00:00
cctest	CPU profiler: increase the max number of captured frames.	2014-06-24 16:00:51 +00:00
fuzz-natives	Fix typo in test/fuzz-natives/testcfg.py	2014-05-30 09:31:44 +00:00
intl	Store i18n meta data in hidden symbols instead of js accessible properties	2014-04-01 10:56:16 +00:00
message	Clean up some A64 specific code in common code that was introduced by A64 merge	2014-02-12 13:27:13 +00:00
mjsunit	Do not unnecessarily expose execution state in debug event data.	2014-06-25 09:13:09 +00:00
mozilla	Throw syntax error when a getter/setter has the wrong number of params	2014-06-17 07:23:26 +00:00
preparser	Throw syntax error when a getter/setter has the wrong number of params	2014-06-17 07:23:26 +00:00
promises-aplus	Stop using urllib.urlretrieve() directly.	2014-05-21 09:25:05 +00:00
test262	Stop using urllib.urlretrieve() directly.	2014-05-21 09:25:05 +00:00
webkit	Throw syntax error when a getter/setter has the wrong number of params	2014-06-17 07:23:26 +00:00