public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Sidharth Jandhyala" <sidharth@clarinox.com>
To: <ecos-discuss@sources.redhat.com>
Cc: <gokhan@clarinox.com>
Subject: [ECOS] Problem with printf
Date: Tue, 18 May 2004 09:02:00 -0000	[thread overview]
Message-ID: <200405180741.i4I7fDM00387@mail002.syd.optusnet.com.au> (raw)


Hi,

I am having a peculiar problem with printf. I noticed that a newline '\n'
must be placed at the end of each printf statement to work. How do I get
around this problem? Here is s sample code

I am using the eb40A board and debugging using arm-elf-insight.


//---------------------------------------------------------

#   include <cyg/kernel/kapi.h>
#   include <stdio.h>
#   include <stdlib.h>

int main (int agrc, char * argv[])
{
        printf("1.HEllo world..........\n");
        printf("\n2.Hello world again");
        printf("3.Hello world again");

}  //End main

//---------------------------------------------------------

The output is 

//---------------------------------------------------------

  1.HEllo world..........

//---------------------------------------------------------

Why has eCos been implemented such that the '\n' must be included at the end
of the printf statement. Is there a way to avoid this characteristic. Is
there a way to flush the print buffers other than looking for the '\n'. 

Thanks in advance.


Regards,


Sidharth


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2004-05-18  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18  9:02 Sidharth Jandhyala [this message]
2004-05-18 11:38 ` Nick Garnett
2004-05-19  8:07   ` Sidharth Jandhyala
2004-05-19  9:39     ` sandeep
2004-05-31 10:41   ` Gokhan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200405180741.i4I7fDM00387@mail002.syd.optusnet.com.au \
    --to=sidharth@clarinox.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gokhan@clarinox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).