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

bv.arch.intrinsics locked to first seen architecture in tabs

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp, python

Research direction

Reproduce the issue by opening binary views with different architectures in separate tabs and checking bv.arch and len(bv.arch.intrinsics) in the built-in Python interpreter. Trace how the active tab supplies bv.arch and its intrinsics; done means switching tabs updates both values to the associated binary view's architecture.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: 5.4.10292-dev Ultimate
  • OS: MacOS
  • OS Version: 26.5.2
  • CPU Architecture: M4 Max

bv.arch.intrinsics is locked to first seen architecture. Opening and switching to another tab with a different architecture binary view keeps the bv.arch.intrinsics from the first seen tab.

Steps To Reproduce:

  1. Open binary view in UI with architecture A
  2. Note the following in the built-in python interpreter:
>>> bv.arch
<arch: x86_64>
>>> len(bv.arch.intrinsics)
11930
  1. Open another binary view in a different tab with architecture B
  2. Note the following in the built-in python interpreter:
>>> bv.arch
<arch: x86_64>
>>> len(bv.arch.intrinsics)
11930

The above was repeated with x86, arm64 and hexagon combinations. Doesn't seem to be specific to an architecture.

Expected Behavior:
bv.arch.intrinsics is updated based on the binary view associated with the open tab.

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.