AW: AW: [En-Nut-Discussion] fprintf() on streamed TCP socket

[Oliver Schulz]

Hi Dusan,

I already found the bug...

The new %P handling in putf from Ralph Mason uses the internal 16 bytes
sized buffer. Bytes from prog mem are copied into this buffer, until it's
full. Then the buffer is put out with an (indirect) call to
NutTcpDeviceWrite.
If the next byte of the string is the termination char, NutTcpDeviceWrite is
called again with length set to zero, and that causes the output buffer to
flush.

A new version (1.6) of crt/putf.c has committed to CVS. Please check it out
and rebuild the libs.

Regards,
Oliver.