Vector35 / Vector35/debugger

Support page level RWX breakpoint

Open
#970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

like x64dbg does. Basically it sets the page to e.g., not executable and it will trigger an exception when the instruction is executed

We can also then extend this to the module level

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 investigating how the debugger represents breakpoints and page memory permissions, using x64dbg's page-level RWX breakpoint behavior as the reference. Define how an execution exception should be reported when a protected page is executed, and clarify whether module-level support is part of the same change. Done means page-level RWX breakpoints work reliably and their exception behavior is covered.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.