From mboxrd@z Thu Jan  1 00:00:00 1970
From: rodrigc@gcc.gnu.org
To: rodrigc@gcc.gnu.org, doug.hackworth@nomos.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, wjtomer@nomos.com
Subject: Re: c++/3056: gcc 2.95.3 -- atexit not catching exit() call following longjmp
Date: Fri, 07 Sep 2001 21:47:00 -0000
Message-id: <20010908044753.29862.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-09/msg00158.html
List-Id: <gcc-prs.sourceware.org>

Synopsis: gcc 2.95.3 -- atexit not catching exit() call following longjmp

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Fri Sep  7 21:47:52 2001
State-Changed-Why:
    I cannot reproduce your problem with gcc 3.0.1 under Linux.
    
    When I compile your testcase, the program never exits,
    it just keeps looping (which I think is the correct behavior):
    
    Try One
    SETTING FOR TERMINATION
    SETTING AFTER TERMINATION 0
    Try Two
    SETTING FOR TERMINATION
    SETTING AFTER TERMINATION 0
    Exiting...
    SETTING FOR TERMINATION
    SETTING AFTER TERMINATION 0
    Exiting...
    SETTING FOR TERMINATION
    SETTING AFTER TERMINATION 0
    Exiting...
    
    Can you try gcc 3.0.1 under Solaris and see if the
    bug is still there?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3056&database=gcc