Differences when decompile with Baksmali 1.2.6 and 1.2.8

[GoogleCodeExporter]

What seems to be the problem?
I decompile framework.odex and android.policy.odex with Baksmali 1.2.6 and 
Baksmali 1.2.8.
Next I compared the smali files with Winmerge and noted that some files have 
differences.
Why this happens?
Which version should I use to ensure that the smali files are correct?

What is the exact smali/baksmali command that you ran?
java -jar baksmali.jar -c [BOOTCLASSPATH] -x [file].odex -o [output]

What version of smali/baksmali are you using? What rom are you working
from?
Baksmali 1.2.6 and 1.2.8 / Android 2.2.1 froyo

Regards

Original issue reported on code.google.com by ling.f...@gmail.com on 7 Sep 2011 at 9:50

[GoogleCodeExporter]

Can you give an example of such a difference?

Original comment by jesusfreke@jesusfreke.com on 7 Sep 2011 at 8:19

[GoogleCodeExporter]

Original comment by jesusfreke@jesusfreke.com on 7 Sep 2011 at 8:19

• Changed state: Pending

[GoogleCodeExporter]

Hi,

Thanks for your reply.

In attached I send you some examples as requested.

Original comment by ling.f...@gmail.com on 7 Sep 2011 at 8:53

Attachments:

• diferences.zip

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The field related differences in there are due to a minor change in the way the 
odexed field accesses are resolved. In those particular cases, I believe either 
set of code is correct and should work fine. However, there were some rare 
cases in 1.2.6 where it was resolving fields incorrectly, which is fixed in 
1.2.8.

Here is the related issue report and changelist:
http://code.google.com/p/smali/issues/detail?id=75&can=1
http://code.google.com/p/smali/source/detail?spec=svna91109b8a76def18c4d0342a44a
87ad270d379ab&r=a91109b8a76def18c4d0342a44a87ad270d379ab

Original comment by jesusfreke@jesusfreke.com on 7 Sep 2011 at 9:04

• Changed state: Done