Vector35 / Vector35/binaryninja-api
Cross-platform Support for Windows Memory Dumps
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Hi there,
I want to disassemble a memory dump of a PE file. Upon startup binary ninja goes into a hex view without identifying any functions. I guess the disassembler knows that this is a PE file, because in the bottom-right corner it shows me two options "Raw" and "PE". However, switching to PE doesn't change anything ("Raw" remains as the selected option).
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
Reproduce the reported behavior by opening a Windows memory dump of a PE file and comparing the hex view's "Raw" and "PE" options. Start from the disassembler's PE recognition and memory-dump handling paths; done means the dump is identified as PE and functions are shown instead of an unchanged raw view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100