Cross-platform Support for Windows Memory Dumps

Open
#653 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
reverse-engineering

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.

Description

Component: Core Effort: Medium File Format: PE Impact: Low

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).

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.