Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Thu, 30 Jun 2005 23:23:27 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Please try latest snapshot -- pthreads mutex users please note Message-ID: <20050701032327.GA14295@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.8i We're coming close to a 1.5.18 release. Please try the latest snapshot at http://cygwin.com/snapshots/ and help verify that there are no regresions against 1.5.17. I'm particularly interested in hearing if the changes made (at users's requests) to the default mutex handling in pthread.h are working correctly. Specifically, does this: Index: include/pthread.h =================================================================== RCS file: /cvs/uberbaum/winsup/cygwin/include/pthread.h,v retrieving revision 1.21 retrieving revision 1.23 diff -u -d -1 -r1.21 -r1.23 --- include/pthread.h 2 May 2005 03:50:09 -0000 1.21 +++ include/pthread.h 11 Jun 2005 04:56:36 -0000 1.23 @@ -55,3 +55,3 @@ #define PTHREAD_MUTEX_NORMAL 2 -#define PTHREAD_MUTEX_DEFAULT PTHREAD_MUTEX_ERRORCHECK +#define PTHREAD_MUTEX_DEFAULT PTHREAD_MUTEX_NORMAL /* this should be too low to ever be a valid address */ do what was requested? This simple change required a lot of changes in the cygwin test suite so I'm not entirely convinced that it was a good thing yet. cgf -- 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/