microsoft / microsoft/vscode-cpptools
Unable to start debugging in macOS Big Sur
Open
Nobody has claimed this yet.
debugger
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: LLDB
Describe the bug
- OS and Version: macOS Big Sur 11.2
- VS Code Version: 1.53.2
- C/C++ Extension Version: 1.2.1, 1.2.2-insiders
- A clear and concise description of what the bug is.
Last few days (seems that it started to happen after update to 1.2.x version iam no longer able to debug c++. Even stopAtEntry simply does nothing and after i quit exe i lunched through vscode and wanted to debug (no changes in config happened) vscode just stays in debug mode (with little stop, restart, step in etc widget open).
To Reproduce
Just try to start debugging of app using F5, seems that lldb debugger does start (i can see it in system monitor) but vscode never attaches to it or is unable to communicate.
Additional context
log.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by starting the C++ app with F5 on macOS Big Sur, then inspect the attached log.txt and the LLDB startup or attachment path. Done means the debugger attaches reliably and the normal stop, restart, and stepping controls work without leaving VS Code stuck in debug mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos, vscode
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100