waitOnNormalExit debugOption missing / not working

[MrAlexBailey]

Environment data

• VS Code version: 1.28.0
• Extension version (available under the Extensions sidebar): 2018.9.0
• OS and version: Windows 7
• Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: N/A

Actual behavior

Running debugger does not wait on exit and instantly closes after the file finishes running.

Expected behavior

Debugger would wait on exit so that debug console could be used to evaluate variables in the file that was previously run.

Steps to reproduce:

1. Create basic python script:
   foo = True
   bar = False

2. Do not use any breakpoints and run debugger

3. Attempt to evaluate print foo in the debug console

4. Console warns: "Please start a debug session to evaluate"

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Starting Microsoft Python language server.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

log.ts:171   ERR Cannot read property 'sendRequest' of null: Error: Cannot read property 'sendRequest' of null
    at t.handleErrorResponse (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2606:480)
    at file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2605:928
    at n.Class.derive._oncancel.then (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:166:736)
    at t.send (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2605:859)
    at t.threads (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2603:565)
    at e.fetchThreads (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2969:99)
    at e.runner (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2970:209)
    at e.doRun (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:205:434)
    at e.onTimeout (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:205:391)
errors.ts:48 WARNING: Promise with no error callback:464
errors.ts:49 {exception: null, error: Error: Cannot read property 'sendRequest' of null
    at t.handleErrorResponse (file:///C:/Users/ab6…, promise: n.C…s.d…e.cancel, handler: undefined, id: 464, …}

[DonJayamanne]

Running debugger does not wait on exit and instantly closes after the file finishes running.

The setting is not necessary. The debug console and terminals are still visible after the debugger runs to completion. This was legacy code brought from VS used to ensure there terminal does not shut down and close, however that doesnt happen in VS Code.

[MrAlexBailey]

They stay open but they are not populated with information and you cannot interact with anything via the console. Is there not a setting to hold the debugger essentially with an implied break at the EOF?

[d3r3kk]

Please put a breakpoint at line 5, then inspect the variables.

[MrAlexBailey]

Please put a breakpoint at line 5, then inspect the variables.

I'm asking if there is a way to emulate that behavior without having to use the breakpoint, which prevents that last line from evaluating and being used in the debug tools.

It would be useful to be able to run an entire file without breakpoints but still be able to interact with it at the end.

[DonJayamanne]

I'm asking if there is a way to emulate that behavior without having to use the breakpoint, which prevents that last line from evaluating and being used in the debug tools.

No there isn't.

[brettcannon]

@MrAlexBailey the closest you might get is that python3 -i will launch the REPL at the end of execution, so you can introspect whatever you want that way.