delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2012/08/13/14:56:29

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+TIwPb1qdp9iMINuA7GhpE
Date: Mon, 13 Aug 2012 14:56:02 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Side-by-side configuration is incorrect reported as permission denied
Message-ID: <20120813185602.GA22085@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CA+7conmVyztppQN8b=aVp6MhPGLGaswkeTFE3tRa7QDHndsH9g AT mail DOT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <CA+7conmVyztppQN8b=aVp6MhPGLGaswkeTFE3tRa7QDHndsH9g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mon, Aug 13, 2012 at 07:56:52PM +0200, Pawel Jasinski wrote:
>hi guys,
>
>is that what we talking about (see patch below)?

Thanks for the patch but I wasn't looking for a simple patch to do this.
I said I'd make the change if someone could suggest a better errno.

When I suggested a patch, it was to somehow change the way Cygwin
reported errors so that Windows errors could be exposed to programs that
aren't expecting them.  I was willing to look at an implementation if
someone was going to take the time to add the non-trivial amount of code
this would take.

>If anybody is concerned about performance, I would be happy to rewrite
>lookup to use some sort of hashing

No thanks.

>I also tried to use koders.com to search for exec* and EACCES.
>It doesn't look like any code indexed by koders is fishing
>specifically for EACCES after call to exec* to do some magic recovery.

That really doesn't prove anything.

cgf

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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019