This question might be better answered on the v8-dev mailing list. The disassembly from --print-code includes a section at the end of a function's code which is labeled "RelocInfo". There are "position" and "statement position" entries with an address (in the generated code) and a zero-based character offset from the start of the script containing the function.
A better way to do it would be to try to use VTune's JIT profiling support. I've never used it so I don't know how well it would work. There are hooks for oprofile support that you can look for in the code. On Tue, Mar 23, 2010 at 3:32 PM, Evgeny Astigeevich <[email protected]>wrote: > Hello, > > I am analyzing performance of V8 by using VTune. I run 'shell.exe with > '--print_code'' and merge VTune data with '--print_code' dump. > How can I get information about correspondence between machine code > and JS source line numbers? > I need the information to figure out which JS constructions cause CPU > stalls. > > Best regards, > Evgeny Astigeevich. > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > > To unsubscribe from this group, send email to v8-users+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users To unsubscribe from this group, send email to v8-users+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
