Vector35 / Vector35/binaryninja-api

Apply TypeLibrary after the fact

Open
#2,773 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: UI Effort: Trivial Impact: Low
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Type libraries are automatically applied when opening up binary. However you might be in the situation where you've opened a binary and applied annotations and then later you want to apply a TypeLibrary. This can be done easily with the API but isn't possible through the UI at the moment.

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 tracing the UI flow that applies a TypeLibrary while opening a binary, then compare it with the existing API path for applying one after opening. Done means the UI can apply a TypeLibrary to an already opened binary while preserving annotations made beforehand; no specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Feature
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.