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

Invalid HighLevelIL tokens at function braces in Pseudo C / Objective C / Rust

Open
#8,443 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c, objective-c, rust

Research direction

Reproduce the error by opening a binary, selecting a High Level IL rendered view, and clicking the outer braces of a function definition in Pseudo-C, Pseudo Objective-C, or Pseudo Rust. Start at HighLevelLanguageRepresentationFunctionGraph and inspect how the brace click resolves HighLevelIL tokens; done means those clicks no longer report an invalid token or the maximum instrIndex.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: at least stable 5.3.9434 -> 6.0.10501-dev
  • Edition: Ultimate
  • OS: macOS 26, macOS 27, Windows

Bug Description:
When double clicking a brace for a function definition inside Pseudo-C, Pseudo Objective-C, and Pseudo Rust, An error occurs:

[Default] Invalid HighLevelIL token exprIndex 11 in HighLevelLanguageRepresentationFunctionGraph of c14 (reported instrIndex 18446744073709551615

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open any binary
  2. Select any rendered view of High Level IL with braces
  3. Click on the outer braces that the function definition lies in

Screenshots/Video Recording:

Image

Additional Information:

What is notable is that the instrIndex is always the 64 bit integer limit.

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.