If I understand the question... You're stepping through machine instructions, and you want to figure out which bytecode handler the code is associated with?
A way to find this in lldb: `e _v8_internal_Print_Code((void*)$pc)/`, which will dump information about the code (ever since v8 5.1.146 / https://codereview.chromium.org/1806883002) --- something similar should work in gdb or msvc's debugger. > On Jun 14, 2018, at 4:33 PM, Thomson Tan <lilo...@gmail.com> wrote: > > I saw some JIT instructions under debugger which seems for the templated > interpreter code. How could I find out which bytecode the binaries > instructions are associated with under debugger? There seems a table with > mapping for each bytecode to JIT code address in isolate. What's the easy way > for doing this? > > -- > -- > 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. -- -- 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.
