X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20a807210910081950v80a4da9ga5ed1265dfca07ef@mail.gmail.com>
References: <20a807210910071714t45136fd7hc36108c990377bc4@mail.gmail.com> 	 <87pr8yqmdt.fsf@uwakimon.sk.tsukuba.ac.jp> 	 <20a807210910080843k50c4cbddtb06ad474b3195a03@mail.gmail.com> 	 <87ws35pwbg.fsf@uwakimon.sk.tsukuba.ac.jp> 	 <20a807210910081950v80a4da9ga5ed1265dfca07ef@mail.gmail.com>
Date: Fri, 9 Oct 2009 06:44:19 +0100
Message-ID: <416096c60910082244k388e8861v84ec7846ecbf9e0a@mail.gmail.com>
Subject: Re: Segfault under cygwin 1.7.62
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
   XEmacs developers <xemacs-beta@xemacs.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

2009/10/9 Vin Shelton:
>>  > #9  0x0056d4d7 in qxe_realpath (path=3D0x22248c "",
>>  >     resolved_path=3D0x22651c
>>  > "c:/cygwin/tmp/s360339.aoa/\201=C3=90\201=C3=90\201=C3=90\201=C3=9002=
ABFx",
>>  >     links_only=3D0) at

>>  > #8  0x0056cd68 in readlink_or_correct_case (name=3D<value optimized o=
ut>,
>>  >     buf=3D0x21e464
>>  > "/tmp/s360339.aoa/\201=C3=AF\217=C2=A3\217=C2=B0\201=C3=AF\217=C2=A3\=
217=C2=B0\201=C3=AF\217=C2=A3\217=C2=B0\201=C3=AF\217=C2=A3\217=C2=B002ABFx=
",

This one looks completely unrelated to the one above.

>>  > #3  0x005151bc in Lstream_really_write (lstr=3D0x176ea00,
>>  >     data=3D0x148d0c0
>>  > "c;C:\\cygwin\\cygwin\\tmp\\s360339.aoa\\=C3=AF\202\201=C3=90\201=C3=
=90\201=C3=90\201=C3=AF\203\22002ABFxi-string)g)=C3=80=C3=A2w\001\200=C3=91=
H\001=C3=82\200\t",

>> and it changes back to something similar but not identical to the
>> original.  Note the "=C3=AF\202" that got inserted somehow.

>> The original
>> stuff at frame #9 is Mule internal coding, but this is not.
>
> are these changes in filename a result of changes in 1.7.62?

What change exactly? What's the original filename here, and how does
it change unexpectedly in terms of POSIX/Cygwin operations? And,
importantly, what's the locale setting?

In a UTF-8 locale at least, there doesn't appear to be a problem with
filename transparency here:

$ echo bla >$'\201=C3=90\201=C3=90\201=C3=90\201=C3=9002ABFx'
$ ls --quoting-style=3Descape
\201=C3=90\201=C3=90\201=C3=90\201=C3=9002ABFx
$ cat $'\201=C3=90\201=C3=90\201=C3=90\201=C3=9002ABFx'
bla
$ rm $'\201=C3=90\201=C3=90\201=C3=90\201=C3=9002ABFx'

Andy

--
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