Status: New
Owner: ----
Labels: Type-Bug Priority-Medium
New issue 922 by [email protected]: V8 profiler can crash with memory
access exception
http://code.google.com/p/v8/issues/detail?id=922
In spaces-inl.h, while recording a stack trace from a profiler tick, the
current execution address in a stack frame is checked to see if it is in
generated code or not. If it is in generated code, it will be in a code
page, which is an 8k aligned page that starts with some identification
information. To decide this, we take the address, which may or may not be
in a code page, and mask away the low 13 bits of it, to get the address
that may be the start of a code page. Then we read from this address. If
the execution address is in C++ code, then this masked address may be in a
different hardware page, which may not be readable, causing a crash. This
has happened, and been debugged to find this issue.
Fix lookup of code pages from addresses so it does not have this issue.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
