Ignore JMP and treat JX==JNX when diffing basic blocks
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
- Tech stack
- java
- Domain
- reverse-engineering
Research direction
No source file, test, or entry point is named. Reproduce the difference in BinDiff 6 on Windows 10 and trace basic-block comparison for terminal JMP instructions, including the JX versus JNX case. Done means blocks differing only in that jump are marked equal while other differences remain visible.
Written by the indexing model from the issue text.
Description
Steps to reproduce the problem:
- Diff a program
- Open a function with some differences
- See some basic blocks which are marked as different only because of the jump at the end
What is the expected behavior?
See the following screenshot:
In such cases, it would be helpful for the blocks to be marked as equal.
What went wrong?
They are marked as different.
What version of the product are you using? On what operating system?
BinDiff 6, Win10.
Ported from b/175509898
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 243
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100