Code-Debug(GDB) no longer stop when program asks for input, but there's no input

[ZZYSonny]

Both my windows and mac have the problem.

In this situation, the program wants to read number for n. But I didn't write anything into the debug terminal. So instead of stopping at that scanf line and wait for input like it did in 0.21.0, code-debug just skip it. And after that, some strange value is given. (Causing my later part to RE)
However, everything is right when I've put freopen at the beginning and prepare for the input.

[WebFreak001]

uh wow this shouldn't happen, nothing even changed there, what's the input if you read a string %s?

[ZZYSonny]

It is still some strange things

[WebFreak001]

that's a command the extension sends, I will look into it

[WebFreak001]

ref @LeszekSwirski

[LeszekSwirski]

Looks like a weird interaction between gdb async and programs reading stdin maybe?

[WebFreak001]

well it should never write to the process stdin because of the special prefixes though, but that could be it

[LeszekSwirski]

Maybe there's some unlucky stdin flushing?

[alianZhen]

It seems need set terminal argument like this "terminal": "".And then it can run in console

[GitMensch]

this is actually the same issue as #262, closing it in favor of it as it contains the "technical reasons for it". And yes: as long as the terminal gets an own pty instead of using GDB console everything works as expected (my personal preference would be to have all program input/output in a new "Terminal" within vscode be default).