Closed GoogleCodeExporter closed 9 years ago
That's exactly what it's supposed to do. Some tools have begun adding a
spurious non-zero value to the link-section value in the header. This is just a
warning that this is the case.
I assume that the apk was otherwise disassembled successfully?
Original comment by jesusfreke@jesusfreke.com
on 7 Dec 2011 at 4:49
I can not make sure whether the apk was disassembled successfully or not, cause
the number of .smali files are much less than .ddx files(I used dedexer to
disassemble this apk).
Cause of that, I guess that the baksmali doesn't disassemble this apk
successfully.
Original comment by ab333...@gmail.com
on 8 Dec 2011 at 1:24
When I disassemble it, I get 391 smali files. Based on the information in the
header, that is the correct number of classes that are defined in the dex file.
Original comment by jesusfreke@jesusfreke.com
on 8 Dec 2011 at 1:30
May I ask the command that you exactly run?
Cause I only get 4 .smali files
Original comment by ab333...@gmail.com
on 8 Dec 2011 at 1:34
The command I ran is simply:
baksmali Droidstats.apk
and then, to check the number of smali files:
find out -type f -name "*.smali" | wc -l
Are you sure you're looking in the right output directory? Using the command
you mentioned in the issue, all the smali files should be located in various
sub-directories of the out directory
Original comment by jesusfreke@jesusfreke.com
on 8 Dec 2011 at 1:42
Sorry , I think I have made a stupid mistake. I found all the .smali files
already.
Very thank for your help
Original comment by ab333...@gmail.com
on 8 Dec 2011 at 1:46
Original issue reported on code.google.com by
ab333...@gmail.com
on 7 Dec 2011 at 10:15Attachments: