Offer to save memroy byte changes caused by the debugger

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

Nobody has claimed this yet.

Assessment

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

Research direction

The issue provides no body, file, test, or entry point to follow. Start by reproducing a debugger session that changes memory bytes, then locate how those changes are tracked and whether the debugger has an existing save workflow. Done should include a reviewed way to offer saving the changes and coverage for the behavior.

Written by the indexing model from the issue text.

Description

enhancement functionality Impact: Medium

This issue has no description.

Dominant language
C++
Stars
331
Forks
33
No merged PRs in 30d

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/debugger

All issues in Vector35/debugger

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.