microsoft / microsoft/vscode-cpptools

nested container not completely visible in debugger

Open
#2,131 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I have an issue with the following structure:
map<set, vector<pair<const Node*, bool>>>

Using the debugging console:
-exec print thisStructure
gives:
$5 = map with 2 elements = {
[set with 1 elements = {"PROD"}] = vector: sz=1, cap=1 = {{
first = 0x7f6f4a501800,
second = false
}},
[set with 1 elements = {"PROP"}] = vector: sz=1, cap=1 = {{
first = 0x7f6f4a4ff000,
second = false
}}
}

It seems like pretty printer is working fine. Unfortunately the output in VS Code is only this:
[{...}]: {...}
[0]
first: 0x7f6f4a501800
second: false

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

Reproduce the nested map<set, vector<pair<const Node*, bool>>> in the VS Code debugger and compare the debugging console output with the variables view. The payload names no source file or test; done means the complete nested container, including both map elements and their children, is visible in the debugger.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.