microsoft / microsoft/vscode-cpptools
Debug Code That Uses Meson & Ninja
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
- OS and Version: Linux Mint 19.3 Tricia
- VS Code Version: 1.41.1
- C/C++ Extension Version: 0.26.3
I want to debug Nemo source code using VSCode.
The way we do it using command line is mentioned in https://github.com/linuxmint/nemo/issues/2309
The summery of the process is -
git clone https://github.com/linuxmint/nemo
cd nemo
sudo apt-get build-dep nemo
dpkg-buildpackage
cd .. && sudo dpkg -i *.deb
One thing we do to save time after the initial build and install using dpkg-buildpackage, is instead run: sudo ninja -C debian/build install
Currently we are using gdb to debug, & G_BREAKPOINT() to set breakpoints. However, it will be great to put breakpoints and press F5 to debug in VSCode. What might be the best possible way to achieve this?
Please let me know if you need any further information to help us with this process.
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
The report describes building Nemo with dpkg-buildpackage, installing with ninja -C debian/build install, and debugging with GDB and G_BREAKPOINT(). Start by tracing how the VS Code C/C++ extension's F5 workflow would apply to that build; done would be a documented, reproducible way to set breakpoints and launch Nemo.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100