The v8::Isolate::CreateParams struct that you can pass to a v8::Isolate has an entry_hook field which can be used to specify a FunctionEntryHook callback, which is a C++ function that will be called at various points during program execution (mostly whenever a new function is entered).
When https://codereview.chromium.org/2733203002 lands, then if you build with GN, passing a custom FunctionEntryHook to newly created Isolates will only work with no-snapshot builds. You can use the GN arg v8_use_snapshot = false to get such a build. GYP builds are not affected by the change at this time. Specifying a FunctionEntryHook has always had the implied effect that an existing snapshot was ignored, and V8 bootstrapped from scratch. The reason for that is that part of the contents of the snapshot have to be different when a FunctionEntryHook is present. The reason the build flag requirement is now being made explicit is because builds with snapshot will lose the ability to bootstrap from scratch, whereas no-snapshot builds will (obviously) retain it. Tracking bug: https://bugs.chromium.org/p/v8/issues/detail?id=6055 Questions, comments, concerns? Please speak up now. Cheers, Jakob -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.