Ben Gruver a91109b8a7 Take into account defining class information when resolving field offsets
This fixes an issue when deodexing, where a field offset is incorrectly
resolved when trying to access a field defined in an ancestor class
when the the child class defines a field with the same name

Kudos to brightidea @ xda-dev for digging into this issue and figuring
out the problem!
2011-08-13 02:22:16 -04:00
2010-08-02 00:58:03 +00:00
2011-07-20 20:13:38 -04:00
2011-01-02 18:39:12 +00:00
Description
smali/baksmali
11 MiB
Languages
Java 52.6%
Smali 45%
GAP 1.6%
Lex 0.4%
Ragel 0.3%