You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
richardfuca opened this issue
Feb 12, 2018
· 1 comment
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Have project open, with "console" in debugger launch configuration set to "integratedTerminal"
Start debugging the program (F5), then quit the application (ex. by using Ctrl-C). Keep the Node Debug Console open.
Try debugging the program again (F5)
OR
Start debugging the program (F5), then click on the Restart button
Expected:
Debugger and program should load like it does in step 2
Actual:
This error occurs:
TypeError: Cannot read property 'toString' of null
at Function.e.isBusy (terminalSupport.ts:56)
at Function.e.runInTerminal (terminalSupport.ts:38)
at _.dispatchRequest (rawDebugSession.ts:393)
at _.e.dispatch (v8Protocol.ts:148)
at _.e.handleData (v8Protocol.ts:104)
at Socket. (v8Protocol.ts:41)
at emitOne (events.js:96)
at Socket.emit (events.js:191)
at readableAddChunk (_stream_readable.js:178)
at Socket.Readable.push (_stream_readable.js:136)
VS Code Info
VS Code version: Code 1.20.0 (c63189d, 2018-02-07T17:09:39.780Z)
OS version: Windows_NT x64 6.1.7601
System Info
Item
Value
CPUs
AMD Phenom(tm) II X6 1090T Processor (6 x 3199)
Memory (System)
16.00GB (10.01GB free)
Process Argv
C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader
no
VM
0%
Reproduces without extensions
The text was updated successfully, but these errors were encountered:
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Feb 13, 2018
I cannot reproduce this problem.
Did you configure the integrated terminal in any way, e.g. by setting a special shell via the "terminal.integrated.shell.windows" setting?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Issue Type
Bug
Description
Steps to Reproduce:
Have project open, with "console" in debugger launch configuration set to "integratedTerminal"
Start debugging the program (F5), then quit the application (ex. by using Ctrl-C). Keep the Node Debug Console open.
Try debugging the program again (F5)
OR
Expected:
Debugger and program should load like it does in step 2
Actual:
This error occurs:
TypeError: Cannot read property 'toString' of null
at Function.e.isBusy (terminalSupport.ts:56)
at Function.e.runInTerminal (terminalSupport.ts:38)
at _.dispatchRequest (rawDebugSession.ts:393)
at _.e.dispatch (v8Protocol.ts:148)
at _.e.handleData (v8Protocol.ts:104)
at Socket. (v8Protocol.ts:41)
at emitOne (events.js:96)
at Socket.emit (events.js:191)
at readableAddChunk (_stream_readable.js:178)
at Socket.Readable.push (_stream_readable.js:136)
VS Code Info
VS Code version: Code 1.20.0 (c63189d, 2018-02-07T17:09:39.780Z)
OS version: Windows_NT x64 6.1.7601
System Info
The text was updated successfully, but these errors were encountered: