-
Notifications
You must be signed in to change notification settings - Fork 210
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
architecture doesn't have reference to the BinaryView #551
Comments
I suspect there's another way around this -- we make Thumb2/Arm work without it, can you clarify a bit more about why you need session data from architecture? |
In smali; strings, methods and other data are stored in their own distinctive tables (arrays). The instructions reference those strings and methods by index. My current idea: save the tables in SessionData, and access it that way. |
I would also like to see this addressed; the primary motivation is so that Python-based plugins could use settings defined for a Resource to change their disassembly format. |
I also have a use case for this, smali is a powerful IL that's used for jvm bytecode transformations and I've been working on jvm bytecode support for some time (on and off, work is crazy). It's quite simple to convert Dalvik and "Java bytecode" to smali and with this change (and a preprocessing step to perform the initial conversion), I believe both Dalvik classes and "Java" classes would be able to leverage the benefits of the different ILs offered (and it would be much more reasonable to do now that projects support has been added) |
Hopefully this issue can be improved, as it greatly limits the flexibility of developing decompilation plugins for unknown instruction sets. |
For a C166 architecture, this will allow proper decoding of sring references which are addressed in a specific bank context. |
This will make certain arches possible - like dex smali.
I need to be able to access bv.session_data.string_table from the Architecture class.
The text was updated successfully, but these errors were encountered: