![](https://secure.gravatar.com/avatar/ff8f665585849e44d8c342bf3b8afd5f.jpg?s=120&d=mm&r=g)
6 Jan
2017
6 Jan
'17
10:42 a.m.
I'm thinking that jitlog.MARK_TRACE_OPT is the only marker I need to keep track of as I'm dumping pycode (overloading execute_frame as vmprof does). When I see a MARK_TRACE_OPT, I just walk backward to find the closest pycode dump. This will give me the actual source code lines that was JITTED. Would this approach work ? Thanks, SHubha