microsoft / microsoft/vscode-cpptools
Nicer workflow for GDB+attach
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Feature Request
I have a Python program that repeatedly compiles C++ code as a shared library, and launches it in a forked process.
The C++ code is run as soon as GDB is attached. I detect this by waiting for SIGUSR1.
In VSCode, I have to press F5, then F6, then Ctrl-Shift-Y, then type "-exec signal SIGUSR1". It would be nice if that sequence of actions could be automatically triggered via launch.json.
Unfortunately, "stopAtConnect" is not working, and neither is
"setupCommands": [
{
"text": "-interpreter-exec console \"signal SIGUSR1\"",
}
]
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 reported F5, F6, and Ctrl-Shift-Y sequence with the GDB attach configuration in launch.json, focusing on stopAtConnect and setupCommands. Compare the configured behavior with manually running -exec signal SIGUSR1; done means the sequence can be triggered through launch.json and the C++ code starts after attachment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100