Closed GoogleCodeExporter closed 9 years ago
You're right, that wasn't a goal when I was writing the code. I'm curious what
exception you are getting? I doubt it would be too hard to fix it so that this
use case is possible.
Original comment by jesusfreke@jesusfreke.com
on 21 Apr 2012 at 9:54
Here's the error I'm getting:
org.jf.dexlib.Util.ExceptionWithContext: Cannot initialize ClassPath multiple
times
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:79)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:104)
at org.jf.baksmali.main.main(main.java:293)
Original comment by rustam...@gmail.com
on 25 Apr 2012 at 2:08
Ah, gotcha. That shouldn't be too hard to fix.
Original comment by jesusfreke@jesusfreke.com
on 25 Apr 2012 at 5:02
It would be really nice if there was an API to smali/baksmali, so that I won't
need to invoke the main() method and simulate command-line invocation, because
in addition to having to simulate the command line, there is also an issue with
System.exit() killing the whole JVM in case of an error :|
Original comment by rustam...@gmail.com
on 26 Apr 2012 at 10:15
[deleted comment]
[deleted comment]
I have examined the code of smali - and it appears that the code is not Thread
Safe - i.e, you cannot decompile two dex files at the same time.
Original comment by oba2c...@gmail.com
on 18 Mar 2013 at 1:52
That is correct :)
This should be considerably improved with the new dexlib2
Original comment by bgruv@google.com
on 18 Mar 2013 at 6:59
Currently smali is thread safe, and it should be safe to invoke multiple
instances of baksmali in the same process. But it's not quite thread-safe to
disassemble multiple classes concurrently using multiple threads in a single
instance of baksmali.
Original comment by jesusfreke@jesusfreke.com
on 7 May 2013 at 8:17
By "currently", I mean in the new 2.0 release (currently in beta)
Original comment by jesusfreke@jesusfreke.com
on 7 May 2013 at 8:17
Great, thanks! will try out when I get a chance!
Original comment by rustam...@gmail.com
on 7 May 2013 at 8:30
Original issue reported on code.google.com by
rustam...@gmail.com
on 21 Apr 2012 at 9:43