X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 22 Dec 2011 15:33:38 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10 Message-ID: <20111222143338.GE31936@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4EF2D79D DOT 2020809 AT shaddybaddah DOT name> <20111222092552 DOT GA31936 AT calimero DOT vinschen DOT de> <4EF3027A DOT 7090503 AT shaddybaddah DOT name> <20111222104443 DOT GC31936 AT calimero DOT vinschen DOT de> <4EF31077 DOT 8060705 AT shaddybaddah DOT name> <20111222111951 DOT GD31936 AT calimero DOT vinschen DOT de> <4EF32BAC DOT 6060209 AT shaddybaddah DOT name> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4EF32BAC.6060209@shaddybaddah.name> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Dec 23 00:07, Shaddy Baddah wrote: > On 22/12/11 22:19, Corinna Vinschen wrote: > > On Dec 22 22:11, Shaddy Baddah wrote: > >> 69 126706 [main] sh 3824 build_env: envp 0x61266AB4, envc 47 > >> 37 126743 [main] sh 3824 child_info::child_info: subproc_ready 0x234 > >> 589 127332 [main] sh 3824 seterrno_from_win_error: > >> /netrel/src/cygwin-snapshot-20111219-1/winsup/cygwin/spawn.cc:692 > >> windows error 5 > >> 59 127391 [main] sh 3824 geterrno_from_win_error: windows error 5 == > >> errno 13 > >> 74 127465 [main] sh 3824 child_info_spawn::worker: CreateProcess > >> failed, Win32 error 5 > >> 196 127661 [main] sh 3824 stat64: entering > > > > Well, CreateProcess fails with "access denied". There must be a reason > > for that, but I don't know what it is and I don't know what to look for. > > Try bisecting the snapshots. > > > * spawn.cc (child_info_spawn::worker): Add CREATE_BREAKAWAY_FROM_JOB > to all spawned processes. Explain why. > > Looks rather innocuous, so don't understand why it is causing me > problems. Indeed. I just tried again on another W7 64 bit machine and it still works for me. I'm wondering if the culprit is a virus scanner or something similar running on your system. Can you please check that? Other than that I might have a solution. I applied a patch which only adds the CREATE_BREAKAWAY_FROM_JOB flag if the calling process is member of a job and the job allows a breakaway. It works in my limited testing, but it would be important to know if it works for you, too, of course. If you're not set up to build your own Cygwin DLL, please test the next developer snapshot. 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