This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: printf() woes

From: Rick Mann <rmann at latencyzero dot com>
To: Matthew Woehlke <mw_triad at users dot sourceforge dot net>
Cc: newlib at sourceware dot org
Date: Wed, 30 Jan 2008 15:34:36 -0800
Subject: Re: printf() woes
References: <49F3286B-A0FA-4710-831E-9075E1392608@latencyzero.com> <fnqr3j$e4e$1@ger.gmane.org>

On Jan 30, 2008, at 1:44 PM, Matthew Woehlke wrote:

Have you looked at the output piped through 'od' (or redirected to a file, and examined in either vim or a hex viewer/editor)? It sure looks like line 1 printed, line 2 printed over top of it, and line 3 printed over top of that... but then I'm not sure what happened. Anyway, the point is it may be that printf works just fine, but your terminal is doing something funny/unexpected displaying the resulting bytes.

Hmm. Well, I wouldn't think any of those lines would cause that, because they all have \n in them. But maybe...

--
Rick

References:
- printf() woes
  - From: Rick Mann
- Re: printf() woes
  - From: Matthew Woehlke

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]