microsoft / microsoft/vscode-cpptools

[WSL] Unable to launch /usr/bin/gdb when setting bash.exe as the integrated shell in VS Code.

Open
#2,811 12 comments 0 reactions 1 assignee View on GitHub

@pieandcakes is already working on this.

Since Nov 15, 2018.

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

Description

I'm unable to launch WSL's installation of gdb when using Visual Studio Code on Windows.

I received an "invalid path" error when I specified this in my launch.json file:

"miDebuggerPath" : "/usr/bin/gdb"

I received an "invalid binary" error when I instead specified this in my launch.json file:

"miDebuggerPath": "/Users/dougdew/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc/LocalState/rootfs/usr/bin/gdb",

I'm running Windows 10 v1803, WSL, Ubuntu 18.04, VS Code v1.29 and C/C++ Extension v0.20.1

I have no other extensions installed.

To reproduce the bug:

  1. Install WSL and Ubuntu 18.04

  2. Install VS Code

  3. Configure VS Code to use the bash shell by adding this to settings:

"terminal.integrated.shell.windows": "C:\WINDOWS\sysnative\bash.exe"

  1. Create directory for cpp project (e.g. /mnt/c/Users/dougdew/Documents/Projects/cpp1)

  2. Create *.cpp file (e.g. main.cpp)

  3. Create tasks.json file with task to build a.out.

  4. Create launch.json file with miDebuggerPath for gdb

  5. Create c_cpp_properties.json file

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.