microsoft / microsoft/vscode-cpptools

local values view dead loop when debug

Open
#13,128 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment
  • OS and version:
  • VS Code:
  • C/C++ extension:
  • OS and version of remote machine (if applicable):
  • GDB / LLDB version:
Bug Summary and Steps to Reproduce

#include <cpr/cpr.h>
#include <cpr/api.h>
#include <cpr/response.h>

int main()
{

std::string a,b;//set break pointer here, when debug, stop here, then local view dead loop 
cpr::Response response = cpr::Post(cpr::Url("http://www.baidu.com"));

return 0;

}

Image

reason is clearly

https://github.com/microsoft/vscode-cpptools/blob/main/Build/lldb-mi/lldb-mi.template.yml
cpptools use old lldb-mi version

Image Image Image

so, why cpptools do not use new version of lldb-mi ???

Debugger Configurations
nothing
Debugger Logs
nothing
Other Extensions

No response

Additional Information

No response

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 local-values dead loop with the C++ sample and inspect Build/lldb-mi/lldb-mi.template.yml, which the report identifies as the lldb-mi configuration. Compare the bundled lldb-mi version and debugger behavior, then verify that stopping at the reported breakpoint no longer traps the local-values view in a loop.

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.