On Wed, Oct 15, 2014 at 3:44 AM, Vyacheslav Egorov <[email protected]>
wrote:
> [...] I will fix this. [...]
>
It might be good to check that IRHydra still likes v8's output. A few weeks
ago I've threaded some information regarding the deoptimization reason
through our deoptimization machinery, so without any tools you'll have a
better idea what's going on and where. The only thing you need to do is add
"--trace-deopt --code-comments", and you get e.g.
...
[deoptimizing (DEOPT eager): begin 0x367a3031 astar.search (opt #6) @53,
FP to SP delta: 140]
;;; deoptimize at <0:4675> bounds-check: out of bounds
...
It's still only semi-user-friendly, but at least it tells you that at 4675
characters from the start of your sources, an out-of-bounds access
occurred. Having to specify --code-comments is still a hack, but we know
how to fix this when we have time (basically push the reason and pop it in
the deoptimization handler).
--
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" 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/d/optout.
