X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 13 Aug 2012 17:14:13 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Side-by-side configuration is incorrect reported as permission denied Message-ID: <20120813151413.GB18354@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5025C431.7050201@cygwin.com> <20120812170641.GC32748@ednor.casa.cgf.cx> <20120813082716.GA11198@calimero.vinschen.de> <20120813144247.GH23253@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Aug 13 07:59, Andrew DeFaria wrote: > On 08/13/2012 07:42 AM, Corinna Vinschen wrote: > >>>There's a difference between cmd and Cygwin. Cmd is a shell, Cygwin is > >>>just the underlying shared lib providing a generic API. > >>OK so bash... > >Ok so bash what? > You were saying cmd is a shell and Cygwin is a shared lib. So then > perhaps the responsibility should fall to bash - a shell... > >>>If an error occurs, it's the shell's responsibility to print an error > >>>message in the first place. All messages printed by Cygwin are not > >>>controllable by the calling application. Therefore we usually only > >>>print messages from the DLL if something very serious happens from the > >>>DLLs perspective. Some arbitrary Windows error code returned from > >>>CreateProcess is usually not something actually serious. There was > >>>just "some" reason that an application couldn't be started. > >>IMHO "some" reason that the user should be alerted about. How is it > >>helpful to the end user to suppress the error message? > >Huh? Somehow you swapping cause and effect. There is no "suppressed" > >error message. Generating an error message is the task of the shell in > >the first place. > There was an error message that cmd showed that bash did not. To me > that's suppression. This is nonsense and you know it. > >It's not that the OS generates an error message and cmd lets it slip > >through while Cygwin (or bash) "suppress" it. It's the CreateProcess > >call which generates an error code ERROR_SXS_CANT_GEN_ACTCTX and cmd > >printing the connected error message, just like bash gets an error code > >EACCES and prints the connected error message "Permission denied". > Plumbing and mechanics aside, I'm just saying the user should be > told the underlying problem. If ERROR_SXS_CANT_GEN_ACTCTX is the > error code could ya at least print that as a string? It would give > the user a fighting change and finding a solution... Plumbing and mechanics is the way to solve the problem. If you don't want to leave the user-only perspective, we will have a hard time to find a solution. > >>I was talking error *messages* not error *codes*. > >Again, cause and effect turned upside down. > I don't think so. We can circle all day around this point. If you don't want to discuss this problem seriously, I'll drop off from this thread. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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