RE: Help needed : Problem with printf

["Banit Agrawal" <banit at cse dot iitkgp dot ernet dot in>]

Hi,

Presently I am testing the libary on a simulator, so I am using the
write stub as system call. When I have to use it with the
board, I am going to use USART for I/O.

Is there any way to test all the library calls for newlib library.
muclibc comes with it's testsuite that provides some testcases. Have
you used that before?

Thanks for your help.

Best Regards,
Banit Agrawal


-----Original Message-----
From: Robles Román, José Miguel [mailto:jmrroman@indra.es]
Sent: Tuesday, August 06, 2002 3:55 PM
To: Banit Agrawal
Subject: RE: Help needed : Problem with printf


Hi,

It depends on the specific application. I usually work in line buffered
mode, but when it is interesting to me seing less than a complete line
(for example in "Select an option: "), I use fflush.

My target is m68k-coff without SO, the I/O is implemented through serial
ports.

Best Regards,
José Miguel

>-----Mensaje original-----
>De: Banit Agrawal [mailto:banit@cse.iitkgp.ernet.in]
>Enviado el: martes, 06 de agosto de 2002 10:07
>Para: Robles Román, José Miguel
>Asunto: RE: Help needed : Problem with printf
>
>
>Thanks, It is working now. It is using buffersize=8 in setvbuf
>function. is it have a optimum value?
>
>-Banit
>
>-----Original Message-----
>From: newlib-owner@sources.redhat.com
>[mailto:newlib-owner@sources.redhat.com]On Behalf Of Robles Román, José
>Miguel
>Sent: Tuesday, August 06, 2002 1:18 PM
>To: newlib@sources.redhat.com
>Subject: RE: Help needed : Problem with printf
>
>
>Hi,
>
>>>   printf("hello world");
>>>
>>> it doesn't print anything in the output.
>>
>>standard output is usually line buffered which means that output is
>>buffered until you print a newline.
>>
>
>If you want to send the buffer to the output device, you may use
>the sentence:
>
>fflush(stdout);
>
>Regards,
>José Miguel
>
>José Miguel Robles Román
>Indra, S.A,
>mailto:jmrroman@indra.es
>San Fernando de Henares
>Madrid, 28760 Spain
>
>