Loading saved results is broken in IDA
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- reverse-engineering
Research direction
Start by reproducing the saved-results workflow in IDA Pro using the listed steps: diff b.idb against a.idb, save the results, restart IDA, and reload them. Compare the reloaded results with the original diff; the issue is done when both produce the same results without the hash warning causing inaccurate output.
Written by the indexing model from the issue text.
Description
Describe the bug
Attempting to load saved bindiff results always yields the incorrect results.
To Reproduce
- Load IDB b.idb
- Diff idb a.idb
- Save results of diff b v a
- Close ida
- Load IDB b.idb
- Load results
Get the following message prompt
The original file hash from the database that is currently loaded is different
from the primary one in the result file:
hash (this IDB)
other-hash (programname.exe, to be loaded)
If you continue, the results will likely be inaccurate.
- Hit continue
8)Results do not match the contents of the diff observed at step 2
Expected behavior
Step 6 and step 2 should yield the same results
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- OS and version: Windows 11
- Locale: US English]
- Disassembler and version: IDA Pro 8.x, IDA Pro 9.x
Additional context
Been this way for a long time.
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/bindiff
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1156 ·
-
[source-shopify] FAILED bulk operation without partialDataUrl is silently treated as successful Openarea/connectors autoteam community connectors/source/shopify needs-triage team/use type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100