Comment 4 for bug 1108717

On 01/29/2013 09:20 AM, Jacobo Aragunde Pérez wrote:

Jacobo,

This is a duplicate bug report. It was first reported about 4 years ago.

We live with it, the solution has been discussed 5 times.

Again by me this morning.

I like to use printf() for debug output, although I did write this code using std:cout.

Somebody else uses something else for debug output. Debug output goes away on a Release
build.

The best thing you can do short term is to not run the Debug build under kicad, but always
from the command prompt.

> If this is just an informative debug message (it looks like that), using
> a non-blocking output function would just do the trick without adding
> more code. A different case is when this output is input to another
> program (could be that eeschema uses it for backwards annotation?).
>
> Can somebody confirm which is the case?
>
>
> More context: the conflicting line is (at PCB_EDIT_FRAME::Remove_One_Track):
>
> D( std::cout << __func__ << ": track " << tracksegment << " status=" \
> << TO_UTF8( TRACK::ShowState( tracksegment->GetState( -1 ) ) ) \
> << std::endl; )
>
> It prints messages like this one:
>
> Remove_One_Track: track 0x29e1170 status=
>