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

Add function not backed by file / Unexpected operation LLIL_SET_REG_SPLIT

Open
#8,399 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp

Research direction

No source file or test is named. Reproduce by loading the reported binary with default settings and with intermediate analysis mode, then inspect phase 2.2 logs around 0x6977dc and the LLIL_SET_REG_SPLIT messages. The issue does not define a requested change or completion condition, so a contributor would first need a maintainer diagnosis.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: 5.4.10303-dev
  • Edition: Ultimate
  • OS: MacOS
  • OS Version: 26.5.2
  • CPU Architecture: M4 Max
  • File: topaz forge strikes quietly

Bug Description:
...
Analysis phase 2.2 starts
...
[Analysis] Attempting to add function not backed by file: 0xff51c0f0
^ handful of these logs
...
[Binary Ninja.LowLevelIl.Expression] Got unexpected operation LLIL_SET_REG_SPLIT in value expr at 0x6977dc
[Binary Ninja.LowLevelIl.Expression] Got unexpected operation LLIL_SET_REG_SPLIT in value expr at 0x6977dc
[Binary Ninja.LowLevelIl.Expression] Got unexpected operation LLIL_SET_REG_SPLIT in value expr at 0x6977dc
[Binary Ninja.LowLevelIl.Expression] Got unexpected operation LLIL_SET_REG_SPLIT in value expr at 0x6977dc
...

Steps To Reproduce:

  1. Load file with Default settings or load file with intermediate analysis mode with function size and time limit disabled.

Expected Behavior:
Reporting in case logs are of interest. Using this file in my unit testing.

Binary:
topaz forge strikes quietly

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.