Follow bash.exe command line changes brought by KB4576484

[gnaggnoyil]

Fixes #49 , #46 , Maximus5/ConEmu#2014 and other similar issues that happens after updating to KB4576484 where wslbridge.exe reports the -v: -c: line 0: unexpected EOF while looking for matching `'' error.

Tested using a build that is built under MSYS2 msys subsystem and no problem other than MSYS2 msys subsystem specific issues occurs.

[gnaggnoyil]

Tested using a build that is built under cygwin and no problems occus.

[xdhmoore]

I can't speak to any other testing, but this PR fixed for me the -v: -c: line 0: unexpected EOF while looking for matching error. Front end built in cygwin.

[arrcher]

Fixes #49 , #46 , Maximus5/ConEmu#2014 and other similar issues that happens after updating to KB4576484 where wslbridge.exe reports the -v: -c: line 0: unexpected EOF while looking for matching `'' error.

Tested using a build that is built under MSYS2 msys subsystem and no problem other than MSYS2 msys subsystem specific issues occurs.

I tried MSYS2 and cygwin builds, both show the same error

Pseudo-terminal will not be allocated because stdin is not a terminal.
wslbridge error: failed to start backend process
note: backend error output: wslbridge-backend: wslbridge-backend.cc:45: int {anonymous}::connectSocket(int, const string&): Assertion `connectRet == 0' failed.

How did you make it work?

[gnaggnoyil]

@arrcher No idea. I haven't met those erros except for the "stdin is not a terminal" one when using an MSYS2 msys build.

What I did was just installing latest cygwin release on my machine and then build wslbridge frontend using that cygwin and then copying wslbridge.exe along with cygwin1.dll to the destination location in ConEmu dir. Have you ever tried replacing %ConEmuBaseDirShort%\wsl\cygwin1.dll with the one you use to build wslbridge frontend?