Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <4fc195f205072117022c16d1e7@mail.gmail.com> Date: Thu, 21 Jul 2005 20:02:58 -0400 From: Fred Smith Reply-To: Fred Smith To: cygwin AT cygwin DOT com Subject: Known issues with Pthreads in 1.5.18? Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j6M03a6S015129 Hi gang! I've been off the list for a few months, just got back on this week. I recall seeing occasional notes about ongoing problems with pthreads way back last winter before I got dropped off the list. Well, I'm checking to see if a multi-threaded program I maintain at work works on the 1.5.x cygwins. I had it working nicely 2-3 years ago on 1.3, but haven't tried since. It runs well on several versions of LInux and on AIX, but am having a problem on cygwin. I can't determine yet if I've got a subtle bug (quite possible) or if there's something whacko in cygwin. I'm hoping some of you can enlighten me as to the state of cygwin's pthreads functions. The program has a particular mutex that fails the SECOND time it is unlocked. I'm at home right now so I don't have the particular error code. It acts like the stack is wedged, because if I put an extra variable on the stack in the routine that calls the pthread unlock function the problem goes away, but so far it has eluded me. I'll keep looking for it, but thought to inquire of any known issues in the pthreads implementation. Thanks! Fred -- 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/