microsoft / microsoft/vscode-makefile-tools
Implement more (or all) from what is supported in launch.json into makefile.launchConfigurations[]
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I am using VS Code (windows) with an ssh connection (ubuntu wsl). Further, I use the makefile tool to compile the program. I can build and debug successfully. The issue is when I want to view the STL (like vector or map)'s values, I see confusing stuff (https://ibb.co/1Qm7GTX).
My settings.json looks like the following:
{
"makefile.extensionOutputFolder": "./.vscode",
"makefile.makePath": "/usr/bin/make",
"C_Cpp.default.configurationProvider": "ms-vscode.makefile-tools",
"makefile.launchConfigurations": [
{
"cwd": "/home/xxx/Repos/xxx",
"binaryPath": "/home/xxx/Repos/xxx/xxx.exe",
"binaryArgs": [],
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
}
],
}
A similar issue is also reported on (https://stackoverflow.com/questions/69586907/how-to-enable-pretty-printing-when-using-the-visual-studio-code-makefile-exten). However, no solutions have been provided.
Any suggestions would be truly helpful.
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 comparing the launch.json capabilities with the fields accepted in settings.json under makefile.launchConfigurations[]. Reproduce the reported STL debugging behavior using the shown Windows-to-WSL setup and determine which launch configuration support is missing; done means the relevant launch.json behavior, including GDB pretty-printing, works through the Makefile Tools configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100