Vector35 / Vector35/binaryninja-api

"Start Full Analysis" from Triage view doesn't start full analysis

Open
#7,578 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

UI: Triage Summary
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.8585-dev
  • Edition: Ultimate
  • OS: OSX
  • OS Version: 26.1
  • CPU Architecture: M3

Bug Description:
After opening a file for triage, navigating to the triage summery, scrolling to the bottom, clicking "Start Full Analysis," and then switching back to linear/graph, all my functions have still only been analyzed with basic analysis and require me to click "Enable full analysis of this function" for each and every one.

Steps To Reproduce:

  1. Open Binja
  2. Click "Triage"
  3. Open a file
  4. Go to triage view (see #7577)
  5. Scroll to the bottom and start full analysis (this should also probably switch us to linear view)
  6. Go back to linear
  7. All functions are "skipped" (see below), seems as though only basic analysis has run

Expected Behavior:
I'd expect for full analysis (not just basic) to have been run for every function, and to be able to see and interact with the decompilation.

Screenshots:
Image

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 by reproducing the issue through the Triage view: open a file, use the triage summary's "Start Full Analysis," then switch to linear or graph view and inspect the functions. Trace the entry point for that action and verify that full analysis runs for every function and that decompilation is available without enabling functions individually.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.