-
Notifications
You must be signed in to change notification settings - Fork 32
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
Strings do not appear to be properly handled in IDA #1
Comments
Hi @mspublic, thank you for the feedback, you're right, this is currently a limitation in the IDA proc. module. The strings in the binary, shown in the Strings windows in IDA ( The data reference feature was disabled because it was not working correctly (we're working on it), it causes IDA to sometimes try to disassemble unaligned addresses (probably due to a logic error in the proc. module) which resulted in much longer analysis times by IDA. I've now enabled it with the use of an environment variable: Also, I've removed a proc. module option ( If you have a particular binary that you can share I'll be glad to take a look at it. |
Sure - if you download the "Hexagon SDK v2.0" (2.0 is important) from https://developer.qualcomm.com/software/hexagon-dsp-sdk/tools You will find some .elf files in there - thats what I was testing one. Im testing to new version now - will let you know how it goes. |
Great, the |
Just tested the new version. Much better in regards to strings! Standard sting references are now picked up just fine. As for performance - during initial loading of the IDB I don't tend to pay too much attention as it takes a while either way. I am using M8974AAAAAAAAQ1234.elf from the SDK. The only side note - the QString references would probably be a nice feature to add - its a reference to a struct/array that references the string. |
Good to know. Thanks again for the feedback. I'm closing this issue, the more general data references issue will be handled separately in #2. Feel free to open a new issue to discuss QString reference support, I'm gonna need more context (I'm not familiar with QStrings) to asses how hard it would be to implement that. |
When loading an elf that has strings - such as the QSR_STRING section. The ASCII strings are not properly detected - and do not appear to show up as ASCII when trying to select as string. Not sure the cause...
The text was updated successfully, but these errors were encountered: