You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we represent addresses within the binary as hexadecimal: extractme.zipmain
...
var_3 = i + 0x804c020;
...
For instance, Binary Ninja prepends in such cases data_ prefix for data.
It would be nice to somehow integrate section information into decompiled code.
Current suggestions were: data_0x804c020 0x804c020 \* data *\ 0x804c020 \* data + 12 *\ - with offset from the section start. ???
Approach
Collect couple of ideas, note them, chose the most optimal 😈 and implement.
The text was updated successfully, but these errors were encountered:
fnhartmann
changed the title
[GUI] Addresses representation in the decompiled code
[Lifter] Addresses representation in the decompiled code
Mar 13, 2024
Proposal
Currently we represent addresses within the binary as hexadecimal:
extractme.zip
main
For instance, Binary Ninja prepends in such cases
data_
prefix for data.It would be nice to somehow integrate section information into decompiled code.
Current suggestions were:
data_0x804c020
0x804c020 \* data *\
0x804c020 \* data + 12 *\
- with offset from the section start.???
Approach
Collect couple of ideas, note them, chose the most optimal 😈 and implement.
The text was updated successfully, but these errors were encountered: