Vector35 / Vector35/binaryninja-api

Crash during long running analysis of Binary View for DYLD Shared Cache with 80 images loaded

Open
#7,830 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Version and Platform (required):

  • Binary Ninja Version: 5.3.8707-dev Ultimate
  • Edition: Ultimate
  • OS: macOS
  • OS Version: 15.1.1
  • CPU Architecture: M1

Bug Description:
Left Binary Ninja running doing analysis on a binary view for DYLD Shared Cache for iOS 26.2 for an iPhone 17 Pro Max, with 80 images loaded.

Steps To Reproduce:
I'm unsure how to reproduce, it just randomly happened.

Binary:
Crash file is uploaded as mystic rain informs attentively

Additional Information:
I had a custom plugin loaded that has many function workflows that modify LLIL and MLIL. I cannot provide any more information or detail. I appreciate I'm not providing much to help fix this issue, I'm just hoping the crash report is enough. I often find doing analysis on large binary views results in a crash and reproducing and root causing is often too much time and effort that I can't put in.

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.

Research direction

Start with the uploaded crash file mystic rain informs attentively and the report's DYLD Shared Cache context: iOS 26.2, 80 loaded images, and a custom plugin modifying LLIL and MLIL. Determine whether the crash can be reproduced or diagnosed from the report, then identify a root cause and confirm that the long-running analysis no longer crashes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.