Long assertion messages don't show up on Windows CE

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Windows Mobile test app with a failing assertion with a really
long message attached to it (say 150 characters)

What is the expected output? What do you see instead?
I expect to see a message about the failing assertion and the message
attached to the assertion. Instead no message is output at all.

What version of the product are you using? On what operating system?
trunk

Please provide any additional information below.
This is a flaw in Windows CE. printf and OutputDebugString have a size
limitation. If you try to output 260 or more characters they output
nothing. I suggest that for Windows CE output be broken up into chunks and
output about 250 characters at a time.

Original issue reported on code.google.com by dalewk...@gmail.com on 12 Sep 2009 at 11:16

[GoogleCodeExporter]

Original comment by zhanyong...@gmail.com on 16 Sep 2009 at 6:20

• Changed state: Accepted
• Added labels: OpSys-Windows, Usability

[GoogleCodeExporter]

FYI, I just saw this also with a gmock failure. The message generated from the 
gmock
failure was 354 characters long so when it failed nothing showed up in the 
output.

Original comment by dalewk...@gmail.com on 23 Sep 2009 at 3:56

[GoogleCodeExporter]

We could create an abstraction layer for gtest's text output.  It will call 
printf() as usual on non-CE platforms, and do something special on CE.

Original comment by w...@google.com on 27 Sep 2010 at 7:05

• Added labels: Priority-Low
• Removed labels: Priority-Medium