public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: assert broken?
Date: Thu, 17 Feb 2011 19:05:00 -0000	[thread overview]
Message-ID: <4D5D7156.2090400@cygwin.com> (raw)
In-Reply-To: <20110217184934.GA25353@home.invalid>

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:
>
> #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.

When an assertion fails, it calls abort().

<http://pubs.opengroup.org/onlinepubs/009695399/functions/assert.html>

Are you saying it's not doing this?

-- 
Larry

_____________________________________________________________________

A: Yes.
> 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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-02-17 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 18:49 Stan
2011-02-17 19:05 ` Larry Hall (Cygwin) [this message]
2011-02-19 18:32 ` Warren Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D5D7156.2090400@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).