microsoft / microsoft/vscode-cpptools
[Debugger] Allow an option to only exit debugging once all inferiors have exited
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
Currently, once a single inferior exits, the entire debugging process exits as well. The only workaround available is to detach inferiors manually with gdb commands before they end. This is particularly problematic when gdb's detach-on-fork mode is turned on in complex programs with multiple fork calls.
The proposed solution is to add some user-facing option that will allow individual inferiors to exit without ending debugging. Since multiple-inferior debugging seems to work fine otherwise, I'm hoping this is possible.
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 issue names no files, tests, or entry points. Start by locating the debugger's handling of GDB inferiors and fork or detach behavior, then determine where the session currently ends after one inferior exits. Done means a user-facing option allows debugging to continue until all inferiors have exited, with coverage for the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100