Launch bash failed when debugging bash on Windows!

[bigtang5]

Unable to start debugging. Unable to establish a connection to GDB. Debug output may contain more ...

The console output:

Starting: "C:\Windows\sysnative\bash.exe" "/usr/bin/gdb --interpreter=mi"
�曪?

"C:\Windows\sysnative\bash.exe" exited with code -1 (0xFFFFFFFF).

the launch.json file content:

"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Bash on Windows Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceRoot}/test.out",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceRoot}",
"environment": [],
"externalConsole": true,
"pipeTransport": {
"debuggerPath": "/usr/bin/gdb",
"pipeProgram": "C:\Windows\sysnative\bash.exe",
"pipeArgs": [],
"pipeCwd": ""
},
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
]

[pieandcakes]

@bigtang5 did you install gdb in bash on windows?

[bigtang5]

Thanks, sure I installed gdb, run gdb in bash: the first line is:
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1

All the Win10 PC have the same bug in my office.

When I input this in CMD window : bash "/usr/bin/gdb --interpreter=mi"
and click, it shows: /bin/bash: /usr/bin/gdb --interpreter=mi: No such file or directory

but list /usr/bin/gdb in bash: ls /usr/bin/gdb
It did exist.

[pieandcakes]

@bigtang5 Sounds like an issue with Bash on Windows? Can you tell me which version you have there so I can try and repro it?

[bigtang5]

Thanks @pieandcakes , my notebook installed the Windows 10,
in bash window:
$ cat /etc/issue
Ubuntu 14.04.5 LTS \n \l

$ sudo lsb_release -a
[sudo] password for tap:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

in CMD window:

c:>bash -version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[mahdibx]

Same problem here, with the same configuration on launch.json, and gdb installed on bash.

Console output :

Starting: "C:\Windows\sysnative\bash.exe" "/usr/bin/gdb --interpreter=mi"
/bin/bash: /usr/bin/gdb --interpreter=mi: No such file or directory
"C:\Windows\sysnative\bash.exe" exited with code 127 (0x7F).

[pieandcakes]

Hi @bigtang5 @mahdibx,

Per our documentation, it looks like at least @bigtang5 is missing "-c" in the pipeArgs field. Can you try and update that and see if that fixes your problem?

[mahdibx]

@bigtang5 I've already tried this, there is no output in the debugger console though, the debugger doesn't crash, but no debugging is going on either, an the program doesn't seem to run at all.
Here is what I tried earlier:

"pipeTransport": {
                "debuggerPath": "",
                "pipeProgram": "C:\\Windows\\sysnative\\bash.exe",
                "pipeArgs": ["-c", "\"/usr/bin/gdb --interpreter=mi\""],
                "pipeCwd": ""
            },

And I tried your solution, but the debugger returns an error:
Unable to start debugging. Unexpected GDB output from command "-environment-cd c:/master". c:/master: No such file or directory.

[pieandcakes]

@mahdibx You shouldn't need to specify "/usr/bin/gdb --interpreter=mi" in your args field. It should be

"pipeTransport": {                 "debuggerPath": "/usr/bin/gdb",                 "pipeProgram": "C:\\Windows\\sysnative\\bash.exe",                 "pipeArgs": [ "-c" ],                 "pipeCwd": ""             },

And I tried your solution, but the debugger returns an error:Unable to start debugging. Unexpected GDB output from command "-environment-cd c:/master". c:/master: No such file or directory.

There is an issue that should be fixed in the next drop with the -envinronment-cd step.

[mahdibx]

@pieandcakes cool thanks for the answers, do you have any idea when the next drop is coming?

[sean-mcmanus]

@mahdibx Should be today.

[xLobito]

Hi.

I used two ways in order to make it work (Which is displayed here as a tutorial and the OP's trying by add the "-c" args into the array), but the result was the same as usual.

Starting: "C:/Windows/sysnative/bash.exe" -c "/usr/bin/gdb --interpreter=mi"
Error: 0x80070057

"C:/Windows/sysnative/bash.exe" exited with code -1 (0xFFFFFFFF).

That's the only output when I try to debug executable (The path is fine). So, I'm with tight hands with nothing to do. Any helps? Very grateful :3.

Greetings from Chile.

@pieandcakes

[bigtang5]

hi @sean McManus:

I have updated to the newest Code version, the bug was still there:

Starting: "C:\Windows\sysnative\bash.exe" -c "/usr/bin/gdb --interpreter=mi"
0x80070057
"C:\Windows\sysnative\bash.exe" exited with code -1 (0xFFFFFFFF).