Open karliss opened 1 year ago
I guess it's related to #713 . Were there any progress towards it?
Not really, it wasn't touched since. Serialization of all of RzIO is big task because of various inherently different modes. But it's possible to do the basic subset serialization first, for the most common tasks.
On Sun, Nov 12, 2023, 13:26 karliss @.***> wrote:
I guess it's related to #713 https://github.com/rizinorg/rizin/issues/713 . Were there any progress towards it?
— Reply to this email directly, view it on GitHub https://github.com/rizinorg/rizin/issues/3967#issuecomment-1807008878, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABRT7ONQ7SX3JV2DTFLRN3YEBMYXAVCNFSM6AAAAAA7DTIKXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGAYDQOBXHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Work environment
rizin -v
full output, not truncated (mandatory)Expected behavior
After loading project raw binary is mapped at the same address it was when saving.
This is important when working with raw MCU firmware binaries. This already annoying while working with single file, and would be even worse if i wanted to map multiple files for main firmware, bootloader and builtin bootloader.
Actual behavior
Binary is mapped at 0
Steps to reproduce the behavior
rizin -a arm -b 16 -m 0x2400 ./testfile
oml
inspect the mapping table, can be also observed by seeking to corresponding position and printing assemblyPs testproj.rzdb
exit
rizin
Po testproj.rzdb
Additional Logs, screenshots, source code, configuration dump, ...