microsoft / microsoft/vscode-cpptools
lldb for Xcode path issue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and version: 13.2.1 (22D68)
- VS Code: 1.75.1
- C/C++ extension: v1.14.3
- OS and version of remote machine (if applicable): n/a
- GDB / LLDB version: lldb-1400.0.38.17
Version: 1.75.1
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:01.965Z (1 wk ago)
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Darwin arm64 22.3.0
Sandboxed: No
Bug Summary and Steps to Reproduce
Bug Summary:
Unable to find GDB in default search path and /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lldb.
Steps to reproduce:
- open https://github.com/ohhmm/generator
- install required cmake, C++ plugins
- build picture-target-generator
- See the error
Debugger Configurations
skryv@HXJG94R2N5 MacOS % ls /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lldb
ls: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lldb: No such file or directory
skryv@HXJG94R2N5 MacOS % find /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ | grep lldb
skryv@HXJG94R2N5 MacOS % find /Applications/Xcode.app/Contents/Developer/Toolchains/ | grep lldb
skryv@HXJG94R2N5 MacOS % find /Applications/Xcode.app/Contents/Developer/ | grep lldb
/Applications/Xcode.app/Contents/Developer//usr/bin/lldb
/Applications/Xcode.app/Contents/Developer//usr/share/man/man1/lldb.1
skryv@HXJG94R2N5 MacOS % lldb -v
lldb-1400.0.38.17
Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
skryv@HXJG94R2N5 MacOS % which lldb
/usr/bin/lldb
skryv@HXJG94R2N5 MacOS %
Debugger Logs
not required, the root cause is known
Other Extensions
No response
Additional Information
LLDB is in the PATH which is reasonable to use in this situation:
% which lldb
/usr/bin/lldb
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
Start by reproducing the debugger discovery with the reported Xcode paths and /usr/bin/lldb, using the lldb -v and which lldb commands from the report. Trace where the C/C++ extension searches for GDB and LLDB, then verify the issue is resolved when LLDB is available through PATH and the documented Xcode location is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100