Cannot undo register value changes

Open
#324 0 comments 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

Start by reproducing a committed register edit and determine which debugger state changes are available before and after the target changes independently. Trace how register edits are recorded and how target state changes are detected. Done means the debugger can offer undo when restoring the previous value is valid, while avoiding restoration when the target has changed.

Written by the indexing model from the issue text.

Description

Effort: Medium enhancement Impact: Low register UI

If I edit the register value and commit it, there is no way to change it back, or undo it.

This sometimes happens to be a reasonable behavior -- since the nature of the debugger is dynamic, if the target has already changed, it may not make sense to restore the register's value to the previous one. However, we should be aware of whether the debugger has changed its internal state and offer to undo the value change when appropriate.

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.