Vector35 / Vector35/debugger

Support manually adding a binary view into the debugger binary view

Open
#477 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement functionality Impact: Medium
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

Right now the debugger dynamically checks the list of loaded modules, and whenever the input file is seen in the list, the binary view for that module is rebased and then added into the debugger binary view. However, this is not enough in several cases:

  1. The user wishes to add multiple binary views into the debugger binary view, e.g., a .exe and a DLL
  2. The user initially does not specify the input module, and later wishes to add a view into the debugger binary view

Note, we should also allow the user to configure whether the option should be repeated when the target is restarted.

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.

Research direction

Start by tracing the existing debugger behavior that watches loaded modules and adds the input module's rebased binary view. Determine the entry point for manually adding multiple views, including a later-selected module, and where restart behavior can be configured. Done means users can add multiple views and choose whether each option repeats after a target restart.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.