Debug adapter should also report the name/index of the register known to the architecture

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
reverse-engineering

Research direction

Start by tracing how the debug adapters report backend register names and how the architecture defines register names and indices. Done means the adapter output exposes the architecture's corresponding name or index as well, allowing static and dynamic analysis information to be combined systematically.

Written by the indexing model from the issue text.

Description

enhancement functionality Impact: Medium register

Right now the debug adapters only report the name of the register reported by the backend, and these are usually the same name as the one used by the architecture. However, the debug adapter should try to unify the two, enabling a more systematic way for the debugger to combine static and dynamic analysis info

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.