From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4F46BD22.60404@domain.hid> Date: Thu, 23 Feb 2012 23:26:42 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4F3BD76C.1040703@domain.hid> <4F3BDC1E.9090707@domain.hid> <4F46B792.8070204@domain.hid> In-Reply-To: <4F46B792.8070204@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Real-time printf in Xenomai 2.6.0 List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jeff Webb Cc: Xenomai help On 02/23/2012 11:02 PM, Jeff Webb wrote: > I was happy to see that printf now works from real-time POSIX threads in Xenomai 2.6.0. Unfortunately, I'm seeing some strange behavior that surfaces when I try to print the string "\n" by itself. When I run the attached example program, I get: > > $ ./printf_test > start > CPU time limit exceeded > $ > > IfI replace the two printf calls with rt_printf calls and #include ,I get the expected result: > > $ ./rt_printf_test > start > 1 > 2 > 3 > 4 > ^C > $ > > The original example also works if these two lines: > > printf("%d", count); > printf("\n"); > > are replaced with: > > printf("%d\n", count); > > Can someone confirm if this a bug in Xenomai 2.6.0, something specific to my HW/SW installation, or some mistake in my test program? I would bet the call to printf is replaced with something else (such as putchar). Could you disassemble the test to check this? Note that I have fixed similar issues in xenomai-2.6 current repository, so you could give it a try. -- Gilles.