This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Segmentation fault when exception is thrown or assertion fails [g++/gcc]
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 4 Jul 2009 23:26:25 -0400
- Subject: Re: Segmentation fault when exception is thrown or assertion fails [g++/gcc]
- References: <a15a61310907042018t40f47459m6054bb3772ff62d5@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On Sun, Jul 05, 2009 at 04:18:44AM +0100, Roman Werpachowski wrote:
>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.
Please provide these details
|||||||||||||||||||||||||||||||
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
--
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