Part of the work for adding AS3 instrumentation for profiling is hooking into the JIT to capture code addresses for functions and file/line mappings. The other part is for interfacing with the profiler's proprietary API, and/or generating profiler-specific symbol files. We need separation of concerns; thus we need a clean API between the two. Requirements: - address range of all code blocks associated with each AS3 function - line/file<-->address mappings, when the AS3 code has OP_debugline/file metadata Soon: - support for unregistering JIT code when it is unloaded. Please add to the list as requirements are surfaced.
You need to log in before you can comment on or make changes to this bug.