Graph is desync'd from Linear view when undefining code bytes.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
Research direction
Reproduce the issue using split graph and linear views, then undefine a selected code range with U and compare navigation in both views. Trace the graph/linear synchronization entry points for undefining code; done means the graph removes the affected code and both views continue to navigate to the same locations.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 5.4.10427 dev
- Edition: Ultimate
- OS: macOS VM
- OS Version: 27.0
- CPU Architecture: m3
Bug Description:
If you undefine code inside of the linear view, they will not be sync'd to the graph display and instead it will keep the old disassembly.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- Split graph and linear views.
- Select a random part of the code
- Press U for undefining it, turning the assembly into bytes
- Click around. If you click around linear, it will not move the graph. If you click in the graph, it will move the linear view to wherever the old instruction used to be.
Expected Behavior:
Expected behavior is that the graph would lose that portion of the code and would remain sync'd with changes to the assembly.
Screenshots/Video Recording:
Additional Notes:
I tested 5.3.9434-stable and this issue is also present.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 20
Contributor guide
No contributing guide indexed for this repository
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 Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8441 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8404 ·
All issues in Vector35/binaryninja-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·