microsoft / microsoft/vscode-cpptools

Search the system path for `program` in `launch.json`

Open
#7,451 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger Feature Request
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: Feature Request

I currently have a launch.json set up for debugging a native Node.js addon on both Linux and OS X with gdb and llvm. Debugging a Node.js addon requires loading the main node executable which in turn dynamically loads the addon which is a shared library. So I have:

"type": "cppdbg",
"request": "launch",
"program": "/usr/bin/node",

which requires the full path to the program being debugged. Both gdb and llvm search the system path when invoking gdb node or llvm node, however the VSCode debugger does not invoke them as it checks that program exists.
Here is my full launch.json - https://github.com/mmomtchev/node-gdal-async/blob/master/.vscode/launch.json

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the launch.json configuration shown in the issue and trace how the cppdbg launch flow validates its program value before starting gdb or llvm. Done means a program name such as node can be accepted and resolved through the system path instead of requiring an absolute path.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.