Fix oatdump crash on arm64/arm code.
Also adds 16 bit literal information. Rationale: When "run-away" instructions are disassembled, the literal addresses may go out of range, causing oatdump to crash. This CL guards memory access against the full memory range allocated to assembly instructions and data (it is possible but not really necessary to refine this a bit). Out of range arguments are now displayed as (?) to denote the issue, which is a lot nicer than crashing. BUG=28670871 (cherry picked from commit d3059e77) Change-Id: I322bbdf83509e253430c40428a05c0ad16b81354
Loading
Please sign in to comment