Vector35 / Vector35/debugger

Offer an opton to only annotate the stack frame boundaries and not the stack variables

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

Nobody has claimed this yet.

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

Description

Right now, we have the debugger.stackVariableAnnotations setting which annotate the stack variable with the help of the analysis info. However, it could be inaccurate at times, and the user may wish to disable it. That said, the stack boundaries are less prone to errors, and I believe it would be helpful in most cases. So it would be nice if we can offer a different setting that controls whether we mark up the stack frame boundaries

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 locating the debugger.stackVariableAnnotations setting and the code that annotates stack variables and frame boundaries. Add a separate setting for frame-boundary markup, preserving independent control of variable annotations, and verify that each option produces the expected annotations.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.