Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Graph is desync'd from Linear view when undefining code bytes.

Open
#8,415 0 comments 0 reactions 0 assignees View on GitHub

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

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:

  1. Split graph and linear views.
  2. Select a random part of the code
  3. Press U for undefining it, turning the assembly into bytes
  4. 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:
Image

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.