search for: libangraybird

...o arm instructions. I think it is not a good idea for our translator to rely on the implementation of llvm ARM back-end. So I have to find another decoder or implement it by by ourselves. Thanks, David [*] For most case, the targets are the shared libraries in Android APKs developed by NDK, like libangraybird.so. I think most of them are pre-linked, so it is bad for us. Because there is no $a, $t and $d symbols, we cannot figure out which region is arm code or thumb code statically. On Thu, Jun 7, 2012 at 8:11 PM, Tim Northover <t.p.northover at gmail.com>wrote: > Hi David, > > On Thu,...

...implement it by by ourselves. > > > Every MCInst created by the MCDisassembler will have a one-to-one mapping > to an actual ARM instruction. > > > Thanks, > David > > [*] For most case, the targets are the shared libraries in Android APKs > developed by NDK, like libangraybird.so. I think most of them are > pre-linked, so it is bad for us. Because there is no $a, $t and $d symbols, > we cannot figure out which region is arm code or thumb code statically. > > > On Thu, Jun 7, 2012 at 8:11 PM, Tim Northover <t.p.northover at gmail.com>wrote: > >&...

...to find another decoder or implement it by by ourselves. Every MCInst created by the MCDisassembler will have a one-to-one mapping to an actual ARM instruction. > > Thanks, > David > > [*] For most case, the targets are the shared libraries in Android APKs developed by NDK, like libangraybird.so. I think most of them are pre-linked, so it is bad for us. Because there is no $a, $t and $d symbols, we cannot figure out which region is arm code or thumb code statically. > > > On Thu, Jun 7, 2012 at 8:11 PM, Tim Northover <t.p.northover at gmail.com> wrote: > Hi David, &g...

...t it by by ourselves. > > Every MCInst created by the MCDisassembler will have a one-to-one mapping to an actual ARM instruction. > >> >> Thanks, >> David >> >> [*] For most case, the targets are the shared libraries in Android APKs developed by NDK, like libangraybird.so. I think most of them are pre-linked, so it is bad for us. Because there is no $a, $t and $d symbols, we cannot figure out which region is arm code or thumb code statically. >> >> >> On Thu, Jun 7, 2012 at 8:11 PM, Tim Northover <t.p.northover at gmail.com> wrote: >&...

Hi David, On Thu, Jun 7, 2012 at 10:17 AM, Fan Dawei <fandawei.s at gmail.com> wrote: > Could you please tell me more about $a, $t and $d symbols? How these symbols > are used to define different regions? Where I can find this symbols in ELF > object file? At the start of each range of ARM code, an assembler or compiler should produce a "$a" symbol with that address, and

Hi Tim, Thanks a lot for the reply. I tested libc.so which is a shared library. llvm-objdump also report some disassemble errors. Could you please tell me more about $a, $t and $d symbols? How these symbols are used to define different regions? Where I can find this symbols in ELF object file? Thanks, David I'm now try to find a decoder of ARM instructions in oder On Thu, Jun 7, 2012