Fix GC issue
authorsgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 25 May 2010 09:18:08 +0000 (09:18 +0000)
committersgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 25 May 2010 09:18:08 +0000 (09:18 +0000)
commit10f1cab4bb3cf43eae1c9095eb21c51b1d8ec452
tree5ba047aad6c5a9a3b66506fe0669a5f3736dd360
parent45c7a14d27b519c984b575cae4d5e9d210e17b05
Fix GC issue

A raw pointer was used while collecting a stack trace. This was not safe as the code collecting the stack trace allocated memory.
Review URL: http://codereview.chromium.org/2147005

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4712 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/top.cc