X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 11 Aug 2010 10:14:56 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set Message-ID: <20100811141456.GD1943@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3C031C390CBF1E4A8CE1F74DE7ECAF3A140684F0AA AT MBX8 DOT EXCHPROD DOT USA DOT NET> <20100811054434 DOT GC32531 AT ednor DOT casa DOT cgf DOT cx> <4C6283FC DOT 4090103 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C6283FC.4090103@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Wed, Aug 11, 2010 at 04:05:32AM -0700, Daniel Colascione wrote: >On 8/10/10 10:44 PM, Christopher Faylor wrote: >> On Tue, Aug 10, 2010 at 09:53:46PM +0000, John Carey wrote: >>> Thanks for the test case for the CreateFile() problem; I used it to >>> create the following test, in which Windows 7 CreateFile() fails with >>> ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL: >> >> As Corinna said: If you are mixing Windows calls with cygwin calls you >> are far into unsupported territory. Cygwin isn't designed to let you >> seamlessly intermix things like pthreads/signals and the Windows API >> functions. > >Then it seems the website needs to be updated. One of the major selling >points of Cygwin, as it were, is the ability to interact with the >Windows API world as well as the POSIX one: "Because processes run under >the standard Win32 subsystem, they can access both the UNIX >compatibility calls provided by Cygwin as well as any of the Win32 API >calls. This gives the programmer complete flexibility in designing the >structure of their program in terms of the APIs used. For example, they >could write a Win32-specific GUI using Win32 API calls on top of a UNIX >back-end that uses Cygwin." I've removed that paragraph. Thanks for the heads up. 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