This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Bug printing string where the 128th char is multibyte
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com
- Date: Mon, 4 Jan 2010 22:35:27 +0000 (UTC)
- Subject: Re: Bug printing string where the 128th char is multibyte
- References: <f519c7c31001041418q1c24bae9t237ee637ed20c0f6@mail.gmail.com> <f519c7c31001041425j4d193528gb9aeca0bf41656de@mail.gmail.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