X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=YkRS974mo0X4WOJ+v9Z1Z92i8Gl8K
	roJaW/rOKGpxSDHSvyPjEkO9sFpg1oV5s142y7iVSHko3jrsePsCufIhV5CJQe2O
	zJtNSgyH09xWQ60o0ebgtxx/buXwRahzVD2+Sv8OpqpL83KrUvqtkFeeMo2Qs8+d
	rMRi+zPs8bt80o=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=d8sE1qz2Ttd9n3EtnU+8fM9RfFU=; b=nun
	3T3mc0UStW+LkxiPp2+neyu7FFKFwQwVf6bGH0vqMfVaInmejZHRLjg18OwM6A4O
	bDvyFsH36/BTthbnYxab0bMn8tAqClv3XcK4D7Zr5ablI9Ek//v51vvTM7Gc2xml
	0uZ5Lodv8bspvfCQt7z5LiV8EbiHcfeqsjbHsGkI=
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
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.1 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*MI:sk:2018090, H*r:172.16.0, Hx-spam-relays-external:172.16.0.1, H*RU:172.16.0.1
X-HELO:	outmail149115.authsmtp.co.uk
From:	David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: Bug Report: Regression in Cygwin 2.11.0-1
Date:	Sat, 1 Sep 2018 16:41:50 +0000
Message-ID:	<E51C5B015DBD1348A1D85763337FB6D901ADFF2257@Remus.metastack.local>
References:	<BL2PR16MB096125DC7F302700C5DE88C0C80E0 AT BL2PR16MB0961 DOT namprd16 DOT prod DOT outlook DOT com> <pmdgjr$9q9$1 AT blaine DOT gmane DOT org> <20180901155435 DOT GL6350 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20180901155435.GL6350@calimero.vinschen.de>
MIME-Version:	1.0
X-Server-Quench:	ee76b257-ae05-11e8-8e1a-9cb654bb2504
X-AuthReport-Spam:	If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute:	OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJa I0lFL1x7O0wTWlBf HTVUBhpUUUISDCNq aQpQZRVcZUBKXg9v UwZLQ1FMFQVtHx4A BAAfUx1tdQBZeTA3 bUcVCDE9GUR6dkN/ SgBQF2sCKzI1b2ZN UkVfalIBcAZXfx4Q Yk13AXJcfGxUNHxl QwU5ZW1pYSNlBXYd aBwCZWgfWUERAmx0 fR0NBzg0BkwCQW0y KVQNO1EDHUBZaANr aB15HAtw
X-Authentic-SMTP:	61633634383431.1039:706
X-AuthFastPath:	0 (Was 255)
X-AuthSMTP-Origin:	213.105.212.114/25
X-AuthVirus-Status:	No virus detected - but ensure you scan with your own anti-virus system.
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id w81Gg9ck030810

Corinna Vinschen wrote:
> On Sep  1 09:56, Andreas Hauptmann wrote:
> > On Sat, 1 Sep 2018 01:24:49 +0000
> > Bryan Phelps wrote:
> >
> > > I'll continue to look around for a more minimal repro,
> >
> > The normalization of paths with backslashes has changed.
> >
> > The following doesn't work any longer:
> >
> >     cd /tmp
> >     stat "..\bin\file.exe" # or
> >     stat "..\\bin\\file.exe"
> >
> > This however still works:
> >
> >     stat "C:\cygwin\bin\file.exe"
> 
> I know where the problem is.  A new piece of code fixing a crash due to a buffer
> underflow is too aggressively guarding the path buffer against this underflow
> when normalizing ".." in Win32 paths.
> 
> I'll fix this and release a 2.11.1 soon, but I still have a question:
> 
> Why do I push out test releases if nobody cares?

Like you, we're a (very) small number of maintainers - and, as far as I'm aware, the command line setup doesn't exactly make continuous integration testing of Cygwin test versions "trivial". I'd love to have had the time within the last 22 days to service my care...

> In terms of this OCAML build system problem:
> 
> Please fix your build system.  Do not mix POSIX and Win32 paths, use POSIX
> paths only.  Backslashes are *no* drop-in replacement for slashes.

The "problem" for us is more subtle than this. The program which is generating that path is not a Cygwin executable, so it is correctly combining a path it has been supplied (the ../stdlib which has been supplied via Cygwin's make) with a filename, so it uses a backslash. It's been on my TODO for years to enhance to understand that the program it's supplying the path back to is a Cygwin executable and so sort it out properly but, well, we're a small number of maintainers! That said, WSL is forcing us to address it properly... 

> Some of the path handling is seriously crippled as soon as you start using
> backslashes, and that's a delipberate decision and won't change, even after
> fixing the aforementioned bug.

I don't quite follow this - does that mean that that path definitely work even with a new Cygwin? i.e. our existing build system is permanently broken for Cygwin 2.11+?


David

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