hosijyun / smali

Automatically exported from code.google.com/p/smali
0 stars 0 forks source link

Compilation produces run-time error #101

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What seems to be the problem?
When recompiling the smali files into a dex file, the compiled dex file causes 
a run-time error crash on many android devices that I have experimented on. 
The run-time error is: arrayStoreException. 
I have done a lot of investigation and have narrowed it down to smali and its 
compilation to dex. This must be the cause of the crash.

What is the exact smali/baksmali command that you ran?
I decompiled a WORKING dex file using:
java -jar baksmali-1.3.0.jar classes.dex -o output
...and then, without modifying the output files, I recompiled via:
java -jar smali-1.3.0.jar -o classes2.dex output
...and when I run my Android application with this decompiled then recompiled 
dex (the dex file that has been through baksmali/smali) it crashes, but the 
default dex works fine. 

What version of smali/baksmali are you using? What rom are you working
from?
1.3.0, I don't know what is meant by ROM in this context.

What is the airspeed velocity of an unladen swallow?
What do you mean, an African or European swallow?

Please provide any additional information below: error messages, symptoms,
etc.

Original issue reported on code.google.com by italia...@gmail.com on 5 Jan 2012 at 1:09

GoogleCodeExporter commented 9 years ago
I meant to add: you can see from my method of deduction that the baksmali/smali 
process is corrupting/polluting the original dex file in some way to cause the 
run-time exception.

Original comment by italia...@gmail.com on 5 Jan 2012 at 1:11

GoogleCodeExporter commented 9 years ago
This does sound like a problem with smali or baksmali, however, you haven't 
provided enough information for me to be able to reproduce or troubleshoot the 
issue.

Can you provide a market link (or web link) to the original application that 
you are working with? Or can you attach the apk to the issue (if you own the 
copyright or have permission from the copyright holder)?

If not, can you try to write a small test application that exhibits the same 
behavior when disassembled+reassembled?

Original comment by jesusfreke@jesusfreke.com on 5 Jan 2012 at 3:07

GoogleCodeExporter commented 9 years ago
@jesusfreke: Please check your email.

Original comment by italia...@gmail.com on 9 Jan 2012 at 5:13

GoogleCodeExporter commented 9 years ago

Original comment by jesusfreke@jesusfreke.com on 12 Jan 2012 at 4:54