This is the mail archive of the
mailing list for the Cygwin project.
Re: assert broken?
- From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 17 Feb 2011 14:04:54 -0500
- Subject: Re: assert broken?
- References: <20110217184934.GA25353@home.invalid>
- Reply-to: cygwin at cygwin dot com
On 2/17/2011 1:49 PM, Stan wrote:
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:
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.
When an assertion fails, it calls abort().
Are you saying it's not doing this?
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple