Debug log from stdio is fragmented

Due to buildbot's design, stdio from application is logged by buildbot, as seen in example:
http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/400/steps/test/logs/stdio

This log is then uploaded to testman, which processes it, looking for specific test strings, formatting it and displaying on testman web interface.

Sysreg at the moment is outputing the ROS debug log to stdio as well as text file. In general, output logged in text file is correct, but one in stdio often is fragmented, by cr/lf introduced in the middle of debug string. It can make either whole test run or at least some of the tests looking like failed.

This error is a blocker for updating to VBox 4.0.x on testbot, as the problem is more severe there, than on v3.12 used at the present moment.

The example could be rev 50969:
http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/397/steps/test/logs/stdio

http://www.reactos.org/testman/compare.php?ids=4836

Running Wine Test, Module: msvcrt, Test: e
n
v
iron
(subsystems\win32\csrss\win32csr\handle.c:113) CsrGetObject returning invalid handle (0)
(subsystems\win32\csrss\win32csr\handle.c:113) CsrGetObject returning invalid handle (5e4)
(subsystems\win32\csrss\win32csr\handle.c:113) CsrGetObject returning invalid handle (5e4)
(subsystems\win32\csrss\win32csr\handle.c:113) CsrGetObject returning invalid handle (0)
OK
environ: 10 tests executed (0 marked as todo, 0 failures), 0 skipped.