Vector35 / Vector35/debugger

Support creating pseudo registers via the API

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

Nobody has claimed this yet.

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

Description

Sometimes certain bits within a register have a special meaning that is not known to the debugger, and the user would want to have a direct visual on them. In such cases, it would be great if we can allow the user to define a pseudo or custom register by supplying the name and expression to compute its value.

This is relevant to https://github.com/Vector35/debugger/issues/230 and https://github.com/Vector35/debugger/issues/466

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 reviewing the debugger API surfaces for register definitions and the related issues #230 and #466. Clarify how a user-supplied name and expression should be represented and evaluated. Done means users can create a pseudo register through the API and obtain a direct visual of its computed value.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.