microsoft / microsoft/vscode-cpptools

Suggestion on Pretty-printer With Pointer Indirection

Open
#5,299 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Type: Debugger

image

Describe the bug

  • OS and Version: WSL Ubuntu 18.04
  • VS Code Version: 1.44
  • C/C++ Extension Version: 0.27.0

This is a feature request. In current version of cpptool, we may utilizing pretty-printer to effectively look at the content of STL structures. However, this mechanism fails as soon as you wrap it with a pointer indirection as shown above.
May we add a feature so that we could find if an underlying type of a pointer could be printed in a better format? Also, if that involves a large amount of work, could we add a menu item Watch Pointee so that we could quickly add "*p" of any pointer-like object to the watch window so we could look at the content more easily?

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 reported behavior in the VS Code C/C++ debugger on WSL Ubuntu 18.04, using the linked screenshot as context. Review how pretty-printers handle pointer indirection and consider the requested Watch Pointee menu item; done means pointer-wrapped STL values can be inspected more effectively or a clear pointee-watch action is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript, vscode
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.