IDB Import should consult type libraries

Open
#6,396 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the IDB/TIL importer and the path that handles unresolved type references. Read the linked TypeLibrary.get_named_type documentation to understand the supplementary lookup, then verify that unresolved references consult type libraries and resolve when a matching named type is available.

Written by the indexing model from the issue text.

Description

Component: DebugInfo DebugInfo: IDB Effort: Trivial Impact: Medium

When loading an IDB/TIL we might not actually have the complete view of all types, therefore we should use a supplementary system for when a type reference would otherwise be unresolved. The most straightforward solution is to consult type libraries when the importer encounters an unresolved type reference.

https://dev-rust.binary.ninja/binaryninja/type_library/struct.TypeLibrary.html#method.get_named_type

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

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.