X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 27 Feb 2009 10:34:01 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [1.7] wctomb bug Message-ID: <20090227093401.GB27879@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Feb 26 21:11, Eric Blake wrote: > Simple test case. This application uses the C locale (by virtue of the fact > that we did not use setlocale(), and evidenced by mb_cur_max of 1). On Linux, > this correctly shows wctomb rejecting the conversion (0x100 is too big to fit > in a 1-byte sequence) with EILSEQ, but newlib currently truncates the invalid > wchar_t value to int and returns 1. Yep, the underlying function _wctomb_r simply assumes that, when running in a single byte locale, all incoming wchars are also just single byte values. I'll create a fix. Btw., you're familiar with newlib, why didn't you just send a patch to the newlib list? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/