Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

local values view dead loop when debug #13128

Open
debugee opened this issue Jan 8, 2025 · 5 comments
Open

local values view dead loop when debug #13128

debugee opened this issue Jan 8, 2025 · 5 comments
Labels

Comments

@debugee
Copy link

debugee commented Jan 8, 2025

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

@debugee
Copy link
Author

debugee commented Jan 8, 2025

I compile new version of lldb-mi, and relpace cpptools's old version, then Local View dead loop bug fixed

@debugee
Copy link
Author

debugee commented Jan 8, 2025

@sean-mcmanus

@debugee
Copy link
Author

debugee commented Jan 8, 2025

@bobbrow
Copy link
Member

bobbrow commented Jan 8, 2025

There's actually an even more interesting comment in that thread. lldb-tools/lldb-mi#115 (comment)

Thank you for bringing this to our attention. (disclaimer, I don't work on the debugger side of the extension)

@debugee
Copy link
Author

debugee commented Jan 9, 2025

There's actually an even more interesting comment in that thread. lldb-tools/lldb-mi#115 (comment)

Thank you for bringing this to our attention. (disclaimer, I don't work on the debugger side of the extension)

can we fix this bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants