[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 208854] run tag shows one output whereas konsole output shows
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2009-09-29 21:30:26
Message-ID: 20090929213026.8107621F95 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=208854





--- Comment #4 from Andreas Pakulat <apaku gmx de>  2009-09-29 23:30:24 ---
(In reply to comment #3)
> (In reply to comment #2)
> > This is not  a bug in KDevelop, but a  bug in your application. We display any
> > output we receive, but we can receive the output only once the output buffer is
> > flushed. If you use printf() you're using stdout which is always buffered, so
> > you have to use fflush(stdout) after printf() to make sure the output is really
> > written out. Or you switch to stderr-printing, which is usually unbuffered. A
> > terminal works a bit differently, thats why it doesn't happen there. You'd see
> > the same thing when looking at the output via <yourapp>|less.
> boost output is out of my hands.

Right, but the above sample code is not. Thats what you need to change.

> afaik, ending the printf line with \n flushs
> the buffer.

No that doesn't necessarily flush the buffer. The only way to flush the buffer
is fflush(stdout).

> if you say it isn't a bug, then ok, you're the boss but it will be hard to
> debug what you can't see...

Right, thats why we can't do anything about it. KDevelop doesn't see the
output, hence it cannot show it.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]