Vector35 / Vector35/binaryninja-api
DWARF Import should be x32-aware
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
What is the feature you'd like to have?
On some 64-bit platforms, it is possible to have 32-bit addressing (e.g. the x32 target). Right now, the DWARF Import plugin will not handle this properly and will, as a result, not correctly recover any information.
Is your feature request related to a problem?
This is related to #2774.
Are any alternative solutions acceptable?
Any solution where this information is correctly pulled out of DWARF and applied to the BinaryView is acceptable.
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 examining the DWARF Import plugin and the related issue #2774. Determine how x32 DWARF information should be recovered and applied to the BinaryView; done means the plugin correctly handles 32-bit addressing on 64-bit targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100