X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 12 Jul 2010 23:11:44 +0100 Message-ID: Subject: Re: pthread_mutex_lock doesn't interrupt From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 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 12 July 2010 17:56, James Cotton wrote: > Hello, I've been trying to get the FreeRTOS Posix simulator to run on > Cygwin and have run into a few bugs in the signal handling/pthread > libraries and have isolated test cases > > I believe when pthread_mutex_lock receives an interrupt it should run > it then resume trying to get a lock Have you got chapter and verse from the POSIX standard on that? By 'interrupt' do you mean SIGINT or any signal? Is it possible that the signal is just being deferred and then subsumed by later signals? Andy -- 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