-
-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can soot still be used now? Do I need to use sootup? #2076
Comments
Soot is still maintained and is updated with bug fixes and occasionally new features. SootUp is a newer version of Soot with a redesigned architecture that shall eventually replace Soot. However, SootUp is not feature-complete. There are things that Soot can do and SootUp can't. For example, SootUp cannot perform instrumentation and write out Java bytecode or Android Dex code. There are quite many features that haven't yet been in the focus of the SootUp team. Another example: We cannot yet port FlowDroid to SootUp. SootUp would first need a proper Android frontend, i.e., one that is not based on dex2jar, plus a few more features here and there. So for the time being, there are two projects in the community. I'm not happy about this, but since both projects are driven by research groups, there is only limited capacity for engineering tasks such as writing frontends, backends, etc. Such work won't give you any scientific merit, so people tend to focus on the features they need to complete for whatever other project they are currently doing. |
I want to know what is the difference between soot and sootup. Is it okay to use the old version of soot?
The text was updated successfully, but these errors were encountered: