Vector35 / Vector35/debugger

Detect mismatch between the file on the disk and in the database

Open
#38 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When the user patched the binary, what is in the database is no longer the same as on the disk. We should let the user know about the situation and decide what to do.

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 how binary patches are written to disk and represented in the database, then identify the entry point where those states can be compared. The issue does not specify the notification, choices, or expected behavior, so the definition of done requires maintainer clarification.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.