Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: bug report: abort in g++ 3.4.4 generated DLL & client
Date: Tue, 2 Aug 2005 20:19:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <42EFC677.2040300@familiehaase.de>
Message-ID: <SERRANONN79xavjrRZ1000000df@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Gerrit P. Haase
>Sent: 02 August 2005 20:16

> Gerrit P. Haase wrote:
> 
>> I get the same result when running a binary compiled with gcc-3.4.4 /
>> binutils-20050608-2 / cygwin-1.5.17, here it is running fine, running
>> the idebntical executable at another box with cygwin-1.5.18 gives me
>> the crash.
> 
> I should mention that it works also the other way round, the biary
> compiled wit gcc-3.4.4 / binutils-20050610-1 / cygwin-1.5.18 is crashing
> but when running it on another machine with cygwin-1.5.17 the identical
> binary works ok.
> 

  I think it's a problem in pthread/mutex stuff.  It's quite likely that it
only shows with more recent gcc because of changes to libstdc++ between
those two versions: I remember seeing quite a lot of work going on there to
do with atomicity, locking and threadsafety.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/