Yes, heap verification is maintained (and is run on our buildbots hundreds of times a day), and when it fails, that's a good indicator that something is wrong.
Of course it's possible that heap verification itself has a bug, e.g. an over-restrictive check; if you have found such a case please let us know. On Mon, May 9, 2016 at 9:32 AM, <[email protected]> wrote: > Dear V8 folks. > > I try to debug V8 using a runtime flag, verify_heap which verifies heap > pointers in case of GC occurs. > > However, I'm not sure if this feature is maintained. > Can I trust its result and conclude that there is something wrong in the > heap in case of it's failed?? > > Thank you in advance. > MyeongBo Shim > > -- > -- > 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/d/optout. > -- -- 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/d/optout.
