Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

vectors and arrays are truncated in debug view.

Aperta
#14,374 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@sean-mcmanus ci sta già lavorando.

Dal 14/4/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug debugger more info needed
Environment
  • OS and version: Windows 11
  • VS Code: latest
  • C/C++ extension: 0.4.6
  • GDB / LLDB version: microsoft debugger
Bug Summary and Steps to Reproduce
Image Problem Summary

When debugging large containers (e.g., vectors with thousands of elements), the VS Code debugger stops displaying element values after an arbitrary index. Instead, entries appear as empty ({}), even though the data is actually present.

Expanding an individual element reveals that the data exists and is correctly populated, which indicates this is a UI/display limitation rather than a data or debugger issue.

Expected Behavior

The debugger UI should:

  • Display values for all visible elements in the watch/locals window.
  • Use lazy loading / virtual scrolling to fetch only the elements currently in view.
  • Dynamically request additional data as the user scrolls.

Actual Behavior

After a certain number of elements, entries are shown as {} (empty).
Values only appear when manually expanding each node.
This makes inspecting large datasets impractical.

Impact

This significantly reduces the usability of the debugger for:

Numerical computing
Graphics / simulation data
Any workload involving large arrays or vectors

Performance optimizations (like limiting displayed elements) should not come at the cost of hiding valid data.

  • Suggested Improvement

Implement viewport-based data fetching:

  • Query debugger engine only for visible rows (with small buffer)
  • Load additional elements on scroll
  • Maintain responsiveness without sacrificing visibility
Lingua principale
TypeScript
Stelle
6.2k
Fork
1.7k
Merge medio
1g 4h
PR unite (30g)
58

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-cpptools

Tutte le issue di microsoft/vscode-cpptools

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.