Comment #2 on issue 2949 by [email protected]:
cctest/test-heap-profiler/TrackHeapAllocations crashes on V8 Linux - nosnap
- debug
http://code.google.com/p/v8/issues/detail?id=2949
The test crashed because we were traversing stack trace when just allocated
object wasn't completely configured, in particular the map pointer was
incorrect. Invalid Map pointer broke heap iteration required to find Code
object for a given pc during stack traversal (in
v8::internal::InnerPointerToCodeCache::GcSafeFindCodeForInnerPointer). The
solution is to report allocation at the moment when we already know address
of the new object but hasn't changed the heap yet.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
