Vector35 / Vector35/debugger

Memory read/writes being shown in a sidebar

Open
#1,196 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

What is the feature you'd like to have?
Memory read/writes being visible to the user so they can see what was written where over time. Could be put in a sidebar.

Is your feature request related to a problem?
No.

Additional Information:

=============== PC = 0x404308
---- W - 0xdeadbeef <- 0xdata_to_write
---- R  - 0xcafebabe <- 0xdata_that_read1
---- R  - 0x1badbeef <- 0xdata_that_read2
=============== PC = 0x404304
---- R  - 0x1badbeef <- 0xdata_that_read2
=============== PC = 0x404300 
---- W - 0xfee1dead <- 0xsome_data
---- R  - .....
...........................

I think something like this would look good UI wise. obviously with real lines not ascii.

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 existing debugger UI and how memory reads and writes are currently recorded or exposed. Define the sidebar's scope, grouping, and update behavior from the examples in the issue, then identify suitable tests or a manual debugging scenario that verifies accesses appear with their program counter, address, operation, and data.

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
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.