microsoft / microsoft/vscode-cpptools

Very slow when view the large-stack-array in debugging program

Open
#448 1 comment 0 reactions 1 assignee View on GitHub

@pieandcakes is already working on this.

Since Jan 17, 2017.

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

Description

VSCode Version: Code 1.8.1 (ee428b0, 2016-12-19T14:41:20.664Z)
OS Version: Linux x64 4.4.0-45-generic

Extensions:
Extension Author Version
compulim-vscode-dictionary Compulim 0.0.5
java-debug DSnake 0.0.2
start-git-bash McCarter 1.1.0
code-settings-sync Shan 2.4.2
logcat abhiagr 0.0.6
code-gnu-global austin 0.2.1
GBKtoUTF8 bukas 0.0.2
vscode-javac georgewfraser 0.0.23
CppSnippets hars 0.0.5
vscode-csscomb mrmlnc 4.0.0
PowerShell ms-vscode 0.8.0
cpptools ms-vscode 0.9.3
vscode-icons robertohuertasm 6.0.0
vscode-header-source ryzngard 1.0.4
guides spywhere 0.6.1
java-imports-snippets tushortz 0.0.1
java-snippets tushortz 0.0.1
cmake twxs 0.0.15
vscode-react-native vsmobile 0.2.5
intelligence-change-case zhengxiaoyao0716 1.1.0
vscode-proto3 zxh404 0.0.7
Steps to Reproduce:
example:
int main()
{
char buf[2048] = "";
return 0;
}

1.debug a c/c++ program.
2.define a large stack array(such as 1024, 2048...102400).
3.set break point below the large-stack-array.launch gdb debug mode with vscode.
4.view the large-stack-array content at the Locals area.

Problem: it 's very slowly to view the large-stack-array when debugging program.
Pls help me to check and solve this problem.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.