[Cdt-launch-inbox] [Bug 115702] New: Output does not appear even after f

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=115702

           Summary: Output does not appear even after flushing cout
           Product: CDT
           Version: 3.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cdt-launch
        AssignedTo: cdt-launch-inbox@xxxxxxxxxxx
        ReportedBy: bl.nero@xxxxxxxxx


In most cases, I can't see output from my programs even if I DO FLUSH the cout.

I set up an managed Make C++ Project, create 'src' source folder and put a file
into it:

test.cpp
----------
#include <iostream>

using namespace std;

int main() {
	cout << "hello!\n";
	cout << flush;
}
----------

And that's all. Moreover, I have the same problems if I do it with
fflush(stdout) and so on, and with many more variations of this simple example.
I'm using Eclipse 3.1 with most recent CDT Release, on WinXP, with Cygwin. My
GCC is:

gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)

Unfortunately, I don't know how to obtain the libc version number.

I have also noticed that the output is SOMETIMES visible. The most typical
situation is when I run an application and get full output (please remember that
it's only a simple hello-world, it's only 1 line). Then, in subsequent runs, I
see nothing. Only after a recompilation, I can see my output ONE time, and then,
on subsequent runs - nothing again.

Also, when I have been experimenting with cppunit, it turned out that the
"empty" cppunit application can sometimes cause some output... Unfortunately, I
don't remember if it was flushed or not, nor can I reproduce it now.

I would VERY appreciate if the Eclipse console DID behave like a typical,
line-buffered terminal, because sometimes people need to debug an application
that utilizes some precompiled libraries that assume we're standing on a typical
environment, and don't flush output every time... Or at least try to fix this
issue...



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.