Vector35 / Vector35/binaryninja-api
DebugInfo needs support for bare Symbols
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Right now some debug file formats may contain symbols and offsets with no other type information associated. However the DebugInfo APIs require you to create a variable (which requires a type). In the future, the DebugInfo APIs should support the creation of symbols as well even if no type information exists.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the DebugInfo APIs and the variable-creation path described in the issue. Determine how bare symbols and offsets should be represented without type information. The work is done when DebugInfo can create and expose symbols that have no associated type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100