Integrated Terminal crashes on startup

[ghost]

• VSCode Version: 1.3.0-insider
• OS Version: Windows 10 Enterprise

Steps to Reproduce:

1. Menu 'View'
2. Submenu 'Views'
3. Click on 'Integrated Terminal
   
   '

[Tyriar]

@profabe can you open dev tools (Help > Toggle Developer Tools) and check for any errors in the console?

[ghost]

@Tyriar many thanks for your quick response. Please see this screenshot.

[Tyriar]

Do you have anything in your user settings.json file?

Also can you check what the %COMSPEC% environment variable points at?

[ghost]

Please see the following screenshots.

[Tyriar]

Does the same thing happen when you add this setting?

"terminal.integrated.shell.windows": "C:\\Windows\\system32\\cmd.exe"

[ghost]

Still happens...

[Tyriar]

Last thing I can think of is try using the 64 bit cmd which is at:

"terminal.integrated.shell.windows": "C:\\Windows\\SysWOW64\\cmd.exe"

Unfortunately this is a bit tricky to debug due to the fix for #6469

Does this also happen on stable, or just insiders?

[ghost]

It happens in both stable and insiders. Please note I just updated them to the latest version and applied the setting regarding 64 bit cmd . I also updated the OS. The error message seems to be different now:

[ghost]

Is there a Developer's Guide available to set up the environment? Perhaps debugging on my machine can help solving that issue.

[Tyriar]

@profabe that won't help much beyond what you can already do. The terminal process (terminalProcess.js), the thing that's crashing, cannot be debugged as it's running in a different process.

Something you could do is make sure that ENV in [terminalService.ts' createTerminalProcess function](https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/terminal/electron-browser/terminalService.ts#L187) is being filled as expected, in particular the PTY*environment variables. You can do this through devtools (Help > Toggle Developer Tools) by adding a breakpoint increateTerminalProcess`.

You can see in terminalProcess.js that %PTYSHELL% is called, passing in the args %PTYSHELLARG1%, %PTYSHELLARG2%, ... and the current working directory is set to %PTYCWD%.

[ghost]

I discovered somethign odd, when debuggng: I can not set a breakpoint at line 146 and 147. Only before and after (sourcemap issue?). Also the env variables are not available in the watch view Did I do something wrong? By the way: This screenshot was taken with stable,

[Tyriar]

I've experienced some issues before with sourcemaps, maybe you could try looking at the .js file and try using the variable name used there?

[ghost]

The debugger only works in *.ts files not *.js files. I also tried to add some console.log statements, but the Developer Tools don't allow saving. Electron seems to be a biest in that matter. Can I somehow build a custom Visual Studio Code with these console.log statements in it?

[Tyriar]

@profabe you can edit the editor files on the OS in an editor that has admin access. You can always build a developer build, it may be more work getting it working though.

[ghost]

@Tyriar thanks for the hint - i managed to console log the variables:

• PTYSHELL: C:\Windows\SysWOW64\cmd.exe
• PTYCWD: c:\Users\Fabian Wohlschläger\Documents\Code\aspnetcore-workshop\MyNewApp

Both paths exist. Does this help to analyse the error?

[Tyriar]

Great thanks. This is a duplicate of #7727 due to the ä. Pretty sure it's an upstream pty.js/winpty issue.