X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
In-Reply-To:	<03ae01c82874$236b2180$2e08a8c0@CAM.ARTIMI.COM>
X-Disclaimed:	61794
To:	"Dave Korn" <dave DOT korn AT artimi DOT com>
Cc:	cygwin AT cygwin DOT com
Subject:	RE: Intermittent 'make' segfaults in Cygwin
MIME-Version:	1.0
X-Mailer:	Lotus Notes Release 7.0.1 January 17, 2006
Message-ID:	<OF1218386E.E77D8CE5-ON8025739A.00385083-8025739A.0038DFB3@accelrys.com>
From:	Stephen Bennett <sbennett AT accelrys DOT com>
Date:	Wed, 21 Nov 2007 10:21:13 +0000
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

>   Try using %CYGWIN%=error_start to get either gdb or dumper.exe 
attached at
> the exact moment of failure.  Check the user guide
> http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
> for full usage information.

Thanks for the tip. That was enough to get a stack trace with no symbol 
information -- not too helpful on its own. When I rebuilt make with debug 
information from the Cygwin source package, I was completely unable to 
reproduce the segfaults -- four complete builds have now succeeded in a 
row, compared with previously when each build would show between 1 and 
about 7 segfaults.

I'd say this is beginning to look like a weird compiler and/or 
optimisation bug, given that it happens frequently with the Cygwin package 
and not at all with an almost un-optimised build (CFLAGS="-O1 
-fno-inline-functions -ggdb3"). Unfortunately I don't have any sort of 
reduced test case demonstrating it, but if I get a chance I'll try to 
narrow down what specifically is triggering it. Is there an easy way to 
find which compiler and optimisation settings were used to build the 
current Cygwin make package?


Accelrys Limited (http://www.accelrys.com)
Registered office: 334 Cambridge Science Park, Cambridge, CB4 0WN, UK
Registered in England: 2326316


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

- Raw text -