X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=4.2 required=5.0 tests=BAYES_00,BOTNET,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,TW_YG
X-Spam-Check-By:	sourceware.org
Date:	Thu, 17 Feb 2011 13:49:34 -0500
From:	Stan <smoore AT exis DOT net>
To:	cygwin AT cygwin DOT com
Subject:	assert broken?
Message-ID:	<20110217184934.GA25353@home.invalid>
Mail-Followup-To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
User-Agent:	Mutt/1.5.17 (2007-11-01)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

I've run cygcheck and tried this on two systems with the same
results; at this point I'm assuming the problem is not local so I'm
not including the typically requested data. I will be glad to follow
up if my assumption turns out to be incorrect.

The issue is triggering an assert dumps core. Trivial test case:

#include <assert.h>

int main()
{
   assert(1==0);
   return 1;
}      

causes a core dump. I originally noticed this is a gdb session and the
triggered assert leaves a bt showing windows info so it looks like the
stack unwinding is having a bad day.

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

- Raw text -