CIO: Problem with 'cerr' output

Itay Chamiel

Hi,

Suppose my code has the following:

cout << "This is good!" << endl;
cerr << "This is bad!" << endl;

The output looks like this:

[C66xx_0] This is good!
[C66xx_0] T[C66xx_0] h[C66xx_0] i[C66xx_0] s[C66xx_0] [C66xx_0] i[C66xx_0] s[C66xx_0] [C66xx_0] b[C66xx_0] a[C66xx_0] d[C66xx_0] ![C66xx_0]

Why is 'cerr' output so different from 'cout'? Can this be fixed?

Thanks,

-itay

over 13 years ago

0 Ki over 13 years ago

TI__Guru**** 472691 points

Hi Itay,

Itay Chamiel said:
Why is 'cerr' output so different from 'cout'?

For a shared output console (multi-core debugging environment where all output goes to one console), CCS will prepend the CPU name before each output to help differentiate between the CPU. Since cerr is unbuffered (unlike cout), you get the CPU name before each character

Itay Chamiel said:
Can this be fixed?

There is an existing request to resolve this. It should be coming in an upcoming CCS update.

thanks

0 Itay Chamiel over 13 years ago in reply to Ki

Intellectual 940 points

Thanks. Is there an issue number so I can track this?

0 Ki over 13 years ago in reply to Itay Chamiel

TI__Guru**** 472691 points

The issue number is: SDSCM00042133

Looks like it is not committed to a specific release yet. I'll see if I can get a confirmation.

Code Composer Studio™︎

Code Composer Studio forum

CIO: Problem with 'cerr' output