X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=3.1 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Sun, 5 Jul 2009 04:18:44 +0100
Message-ID: <a15a61310907042018t40f47459m6054bb3772ff62d5@mail.gmail.com>
Subject: Segmentation fault when exception is thrown or assertion fails  	[g++/gcc]
From: Roman Werpachowski <roman DOT werpachowski AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 get the following output:

      4 [sig] a 1408 _cygtls::handle_exceptions: Error while dumping
state (probably corrupted stack)
Segmentation fault (core dumped)

When running the following test programs:

#include <assert.h>

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

or

#include <cassert>
#include <stdexcept>

int main()
{
    throw new std::runtime_error("Just because"); // the same with
assert(false);
}

I am using gcc-3.4.4.

I understand that Cygwin defaults to dumping the stack trace, but why
the message about segmentation fault? It confuses the hell out of me.

Regards,
Roman Werpachowski

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