X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Eric Blake <ebb9 AT byu DOT net>
Subject:	Re: Bug printing string where the 128th char is multibyte
Date:	Mon, 4 Jan 2010 22:35:27 +0000 (UTC)
Lines:	19
Message-ID:	<loom.20100104T233234-168@post.gmane.org>
References:	<f519c7c31001041418q1c24bae9t237ee637ed20c0f6 AT mail DOT gmail DOT com> <f519c7c31001041425j4d193528gb9aeca0bf41656de AT mail DOT gmail DOT com>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Eduardo D'Avila <erdavila <at> gmail.com> writes:

> I've found a bug that happens when the 128th (index 127 on a 0-based
> string) char of a string is a multibyte char. When I print such
> string, only the multibyte char and the chars after it are displayed.

What you've found is a bug in your own program, at lesat for the BUG.c version 
of your report.

http://cygwin.com/ml/cygwin/2010-01/msg00100.html

Try 'printf ("%s",str)' rather than 'printf (str)' to see the difference.  And 
why 128 bytes into the string?  That's the cutoff of where gcc optimizes a 
printf without % into a puts.

-- 
Eric Blake




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -