Title: Eclipse Console does not sync stdin/stdout correctly on Windows 11 (Eclipse 4.37.0)

[harrivilppola]

Body:
I am experiencing an issue with the Eclipse Console when running Java programs that read user input using and . The console cursor does not move to the correct line before input is requested, even though the program prints newline characters and flushes the output stream.
The same code works correctly in a normal Windows terminal (CMD/PowerShell), so the problem appears to be specific to the Eclipse Console’s handling of stdout/stdin synchronization.
Environment:
• OS: Windows 11
• Eclipse IDE: 4.37.0
• Java: (any version, issue is reproducible across multiple JDKs)
Steps to reproduce:

1. Create a simple Java program that prints a line, flushes stdout, and then calls or similar.
2. Run the program in the Eclipse Console.
3. Observe that the cursor appears on the wrong line or overlaps previous output.
   Expected behavior:
   The cursor should appear on a new line exactly where the program prints the input prompt.
   Actual behavior:
   The cursor appears on the previous line or in an incorrect position, making interactive console programs difficult to use.
   This issue seems related to how the Eclipse Console buffers and renders stdout before stdin is requested.
   Thank you for looking into this.

Let's make sure issue is not already fixed in latest builds first.

• I verified I can reproduce this issue against latest Integration Build of Eclipse SDK

Steps to reproduce

From a fresh installation and clean workspace:

• <...setup environment>

I tried

• <... trigger issue>

I expected: <what was the expected outcome?>

But got: <what is the actual undesired behavior?>

Here is some relevant log output

From <workspace>/.metadata/.log

<relevant log output>

Tested under this environment:

• OS & version: ...
• Eclipse IDE/Platform version (as shown in Help > About): ...
• ...Anything else that can be useful...

Community

• I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.

[fedejeanne]

Thank you for reporting it, @harrivilppola.

It is not completely clear to me how do you reproduce this error, can you please provide a snippet and some screenshots?

[iloveeclipse]

Also please note, 4.37 is not supported, so please provide steps to reproduce in 4.38.

[laeubi]

Pleas also be aware that as you mentioned the

Eclipse Console

is not a

Windows terminal (CMD/PowerShell)

and as such

making interactive console programs

will not work well there (not only since Eclipse 4.37) because it is more like an Editor Document where you can place the cursor anywhere.

If you require true PTY (aka "terminal") you can either open a Terminal View or install the new Terminal Console Support:

https://eclipse.dev/eclipse/markdown/?f=news/4.37/platform.md#support-launching-with-a-terminal-console

but be aware that it might be buggy on windows

• Unable to start program if org.eclipse.debug.terminal is in the target platform #2428

so we would appreciate any testing, feedback and help to improve that feature.