microsoft / microsoft/vscode-cpptools
[Feature Request] Fully support target-async on
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
When the session starts it sends:
-gdb-set target-async on
This is intended to enable asynchronuos commands, see https://sourceware.org/gdb/onlinedocs/gdb/Asynchronous-and-non_002dstop-modes.html
Whether the debugger actually supports it can then be checked using -list-target-features which will respond with something like:
^done,target-features=["async"]
If "async" appears in the target-features list, the debugger supports asynchronuos commands.
However, it never asks to see the supported target-features and starting the debugger and trying to issue commands results in:
Unable to perform this action because the process is running.
Looking in MICore/CommandFactories/gdb.cs in AllowCommandsWhileRunning(), and from what I can see there, it just says false.
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 in MICore/CommandFactories/gdb.cs, especially AllowCommandsWhileRunning(), and trace the session-start commands around -gdb-set target-async on. Review how -list-target-features responses are handled and how running-command permissions are determined. Done means supported async targets are recognized and commands no longer fail solely because the process is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100