microsoft / microsoft/vscode-cpptools
VSCode says : "Debug adapter process has terminated unexpectedly (read ECONNRESET)"
Open
Nobody has claimed this yet.
debugger
more info needed
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Debugger
Describe the bug
- OS and Version: Raspbian Buster
- VS Code Version: 1.28.2
- C/C++ Extension Version: 0.21.0
- When I try to start debugging, breakpoints are not reached with this message :
"Debug adapter process has terminated unexpectedly (read ECONNRESET)"
Launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "C++ Debug (gdb)",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/bin/bin",
"preLaunchTask": "Build C++ project",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "/usr/bin/gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
]
}
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 with the supplied launch.json configuration and reproduce the failure when launching gdb on Raspbian Buster. Check when the debug adapter reports ECONNRESET and whether breakpoints are reached. Done means the same configuration starts debugging without the adapter terminating unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100