as example
i have already idb from ida 83
load into ida 90
after converting it to the new format of ida 90
i goto to function with try/catch
press F5 i got from ida console
could not find valid save-restore pair for rbp
after press button “Reanalyze program”
and wait to finish reanalyze
F5 again and again
i got the same
could not find valid save-restore pair for rbp
if i load original exe file to 90
i see a try/catch
Unfortunately, some information used by the eh34 plugin is only parsed on the initial load and extracting it from old IDB may be difficult or impossible. It is unlikely that we’ll work on this use case unless there is significant demand (and plenty of samples), so for now I’d suggest to transfer information from the old IDB into the new one.
how compatible is idc api < ida 9.0 with idc ida 9.0 >=
because even if compatible
a lot of manual work to remake idc script to apply the same binary loaded from scratch in the new ida 9.x
because by default the exported script
starts to delete the entire database and analyze it again
and if you didn’t know, this resulting analysis is even worse than the primary ida analysis when loading exe
I would like to receive only structures and function names in idc export
so that they can be applied over the same file in the new ida 9.x
and here we return to the topic
about local synchronization between ida
Yes, IDC export is not ideal and was developed back when files were small and not complicated, but it’s better than nothing. You can comment out the parts which you would like to skip. A better database migration feature is on our roadmap although we don’t have a specific date at this time.