Vector35 / Vector35/binaryninja-api
Export names are not properly processed
Open
Nobody has claimed this yet.
Component: DebugInfo
DebugInfo: PDB
Effort: Low
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
For the attached binary, we are not properly processing all of the export functions
We can see the name of the string exists in the binary, but it somehow does not work
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 attached kernel32.dll binary and the export-processing path in the repository. Compare the exports that are present in the binary with those recognized by the API, then identify the relevant existing tests or analysis entry point. Done means all expected export names from the sample are processed correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100