-
Notifications
You must be signed in to change notification settings - Fork 164
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
Save the remapped_binary path and sections to the .ini #97
Comments
Hi, BinCAT supports for mapping chunks from the binary file that is being analyzed, by defining sections in the input file (there's an example here). The format is: section[SECTION_NAME] = VIRTUAL_ADDRESS,VIRTUAL_LENGTH,PHYSICAL_ADDR,PHYSICAL_LENGTH BinCAT doesn't support (yet?) mapping chunks from files other than the binary being analyzed, or a core dump file. So, a dirty hack that will probably work would be concatenating the memory chunks you want to map at the end of the binary file being analyzed. |
Hello, |
@trou Oh, yes. I remember that I unchecked this option because analysis could not start after reloading IDA database:
It works when idb is loaded for the first time. I've fixed it by changing this line to @Lastpixl It works, thank you. I believe "remap binary" approach is more convenient. |
@hardboost thanks for the report. I've improved the situation, now the remapped sections are saved in the IDB and the configuration files has the "remap binary" option state saved. I'm leaving this bug open for now as I want to save the remapped_binary path and sections to the .ini too. |
I need to analyse one function in my binary, but I have to pass pointer to big chunk of memory as an argument. I've created additional segment in IDA and fill it with contents from file. The argument has correct pointer to created segment, but analysis fails with message
[ANALYSIS] interpreter: unreachable state at address ...
right after dereferencing this pointer.Is there a better approach to solve this problem besides creating a very large .init file?
The text was updated successfully, but these errors were encountered: