C::B debug (gdb) remove Console of my host application

[ollydbg]

The log window has some refresh problems on windows, the messages are almost "realtime".
You have to scroll up-down, so the log window can be refreshed correctly...

This is an annoying behavior I have encountered for several years.
I have no idea how to solve this.

[oBFusCATed]

I don't think this is correct behavior.  The "\n" in printf() should cause auto flush.
Could this be improved in the future ?

Can you quote the standard, where you've read this?

[kccheng]

I don't think this is correct behavior.  The "\n" in printf() should cause auto flush.
Could this be improved in the future ?

Can you quote the standard, where you've read this?

I don't have any standard in hand and don't remember where I got this understanding.
After a quick search of my books ... I found something related to this in
W.Richard Stevens' famous book "Advanced Programming in the UNIX Env."
Ch. 5.4 Buffering

Well, I think maybe it's not printf's standard.  Be correctly, the stdout and stderr
are line buffered I/O stream.  So, the question becomes:

Since C::B Debug log console will capture stdout/stderr from debuggee ...
does C::B Debug log console should also behave like a line buffered I/O stream ?
so the debuggee can have similar expectation with/without C::B.

Regards,
KC

[oBFusCATed]

Since C::B Debug log console will capture stdout/stderr from debuggee ...
does C::B Debug log console should also behave like a line buffered I/O stream ?
so the debuggee can have similar expectation with/without C::B.

The log is line buffered I think. Take a look at PipedProcess if you don't believe me.