microsoft / microsoft/vscode-cpptools

Launching the debugger in mode "gdb" hangs forever

Open
#3,353 12 comments 0 reactions 1 assignee View on GitHub

@WardenGnaw is already working on this.

Since Mar 25, 2019.

debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

System information:
-OS: Windows 10
-VS code version: 1.32.3
-Extension: C/C++, version 0.22.1
-Compiler/debugger version: MinGW.org GCC-8.2.0-3

Bug description:
When launching the debugger, configured in mode "gdb", the blue bar is loading forever and nothing happens. I already tried to enable logging but nothing is output to the VS code debug console. However when setting externalConsole to false, the following line is printed in the integrated terminal:

env "c:\Users\brunn\.vscode\extensions\ms-vscode.cpptools-0.22.1\debugAdapters\bin\WindowsDebugLauncher.exe" --stdin=Microsoft-MIEngine-In-fyz0vlaa.gej --stdout=Microsoft-MIEngine-Out-0aiqcb4f.wbn --stderr=Microsoft-MIEngine-Error-gvbsagt3.yu1 --pid=Microsoft-MIEngine-Pid-aqbc4pf3.3dh --dbgExe=C:/Data/Programmes/MinGW/bin/gdb.exe --interpreter=mi

However, this command never terminates and it seems like something goes wrong during the execution of that command.

{
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/main.exe",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "miDebuggerPath": "C:/Data/Programmes/MinGW/bin/gdb.exe",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": false
                }
            ]
 }

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.