microsoft / microsoft/vscode-cpptools

Ability to resolve structure global structure members on mouse-hover

Open
#13,273 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger help wanted
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Feature Request

When I hover the mouse over a structure's member, it shows me the type(which is nice), but often I actually want to see the value of the structure's member.

Example structure definition in header:

typedef struct {
  uint8_t AIFrom;
  uint8_t AITo;
}moveVar;

Example usage site:

extern moveVar moveStatus;

void func(){
  clearChessLEDs();
  convertSendLEDData();
  sequenceAILights(moveStatus.AIFrom, moveStatus.AITo);
}

Hovering on moveStatus.AIFrom shows AIFrom's type:

Image

Note: I'm quite new at using VSCode , it's possible I've made a mistake setting it up. I am using ms-vscode.cpptools version 1.23.6 with an ESP32-S3 hardware target over JTAG. They thought this was an issue in this module.

Contributor guide

Open the contributing guide

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 reproducing the hover behavior with cpptools 1.23.6 on the reported ESP32-S3/JTAG setup, and review the linked vscode-esp-idf-extension discussion. Trace the existing hover resolution for moveStatus.AIFrom and determine what is needed to resolve the global structure member's value; done means the hover displays that value reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.