X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49CBEAA0.9050107@gmail.com> Date: Thu, 26 Mar 2009 20:50:40 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Windows executable fails to write to the registry when run in a cygwin shell but OK from a command prompt References: <49CBDCFA DOT 2050001 AT opensourceinc DOT com> In-Reply-To: <49CBDCFA.2050001@opensourceinc.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Adoram Rogel wrote: > When I run it in a Command prompt - all is well, consistently. > When I run it in a cygwin shell - it fails, consistently. > The uid reported in cygcheck -s and the shell's user is an > administrator, so no such problems should occur. > > Any ideas? where should I start looking? Version of windows? UAC? Behavioural-blocking security software? Simple testcase that uses the same windows APIs to try and write to the registry and fails? Also, you could try running it under strace and looking for win32 errors in the log file. It's possible though that the bug might not appear when launched from strace. cheers, DaveK -- 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/