A follow-up to fix 553: really report function object moves.
authormikhail.naganov@gmail.com <mikhail.naganov@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 22 Jan 2010 09:42:24 +0000 (09:42 +0000)
committermikhail.naganov@gmail.com <mikhail.naganov@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 22 Jan 2010 09:42:24 +0000 (09:42 +0000)
commit40fd97c87df3bf23df279408e7fafb1f54faa1bc
treec81a61edcc523312918d65c26a4e5c9d476b8cef
parent69915136fa1527c9968579c93e51e8d4bf0a30df
A follow-up to fix 553: really report function object moves.

As an afterthought, I realized that I put function objects moves
reporting into a method that deals with only code object moves.  I've
looked up that function objects are allocated in old pointer space and
new space, so I moved logging to the corresponding VM methods.

BUG=553

Review URL: http://codereview.chromium.org/552089

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3679 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/mark-compact.cc
test/cctest/test-log-stack-tracer.cc