microsoft / microsoft/vscode-cpptools
Cannot send ctrl-c or ctrl-break to spawned debug console
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Debugger
-
OS and Version:
Microsoft Windows [Version 10.0.17134.112]
-
VS Code Version:
Version 1.24.1
Commit 24f62626b222e9a8313213fb64b10d741a326288
Date 2018-06-13T17:51:32.889Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64 -
C/C++ Extension Version:
Version 0.17.4
-
Other extensions you installed (and if the issue persists after disabling them):
None
-
A clear and concise description of what the bug is.
Trying to send ctrl-c to debug console but not triggering console interrupt handler in source code
-
Additional context
Tried adding logging to debugger but no events are being captured for this
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 failure on Windows 10 with VS Code 1.24.1 and C/C++ extension 0.17.4, using the debug console and ctrl-c or ctrl-break. Start by tracing the debug console interrupt path and the logging mentioned in the report; done means the source console interrupt handler is triggered by these controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100