Vector35 / Vector35/binaryninja-api

[KernelCache] Improve kernel cache / dyld shared cache triage view symbols list

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

Nobody has claimed this yet.

Effort: Low File Format: KernelCache File Format: SharedCache Impact: Medium
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.2.8611-dev Ultimate, a659259f
  • OS: macos
  • OS Version: 26.1
  • CPU Architecture: arm64

Description:
The behavior when double-clicking on a symbol in the symbol list within the kernel cache triage view is a bit confusing, and there's functionality that seems like it should be present that is missing.

  1. There's no indication whether the library containing each symbol has already been loaded.
  2. Each time you double-click on a symbol you're asked whether to load the image, even if the image is already loaded.
  3. There's no way to navigate from a symbol in the symbol list to the symbol in the linear / graph view.

For 2, double-clicking an image in the image list doesn't prompt the user. It's not clear why we prompt when double-clicking in the symbol list.

For 3, I've heard some suggestion that after double-clicking on a symbol to load an image, subsequent double-clicks on that symbol should instead navigate to the symbol. It's not clear whether it should also navigate the first time.

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 in the kernel cache triage view's image and symbol lists, comparing their double-click behavior. Clarify whether symbols should show loaded-library state and whether the first double-click loads or navigates, then verify the chosen behavior manually for loading, repeated activation, and navigation to linear or graph view.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems, reverse-engineering
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.