Debugger does not send messages over protocol if debugged program does not launch

[DonJayamanne]

• Debug a python file which would not compile (e.g. mixed spaces and tabs)
• pydevd Debugger spits out errors in stdout and process ends

The above workflow is fine when debugging with terminals, as the output in the terminal window has the necessary error message with the stack trace.

However when debugging in VS Code without any terminals, then there's no output. To the user the debugger isn't working (nothing is happening, though in the background it started and died - immediately).

Solution, VS Code adapter expects the output to come over the protocol so the messages can be displayed in the output window.

Note:

• Default behaivour in VS Code extension is to debug without any terminal
• For the experimental debugger the default behavior will be changed to alway use a terminal (this is a work around for this issue as well as Ability to redirect stdout and stderr (tee program output) #60)

[int19h]

Isn't it the same as #55 ?

[DonJayamanne]

Oops, for some reason I assumed I had not created an issue for this.