From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19964 invoked by alias); 20 Feb 2003 17:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19900 invoked by uid 71); 20 Feb 2003 17:06:01 -0000 Date: Thu, 20 Feb 2003 17:06:00 -0000 Message-ID: <20030220170601.19896.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Phil Edwards Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop Reply-To: Phil Edwards X-SW-Source: 2003-02/txt/msg00999.txt.bz2 List-Id: The following reply was made to PR libstdc++/9756; it has been noted by GNATS. From: Phil Edwards To: "Stephen M. Webb" Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop Date: Thu, 20 Feb 2003 12:03:48 -0500 On Thu, Feb 20, 2003 at 11:59:55AM -0500, Stephen M. Webb wrote: > On February 20, 2003 11:25 am, Phil Edwards wrote: > > > > The rethrow never rethrows; it never leaves the try block. Instead, > > the support routine __cxa_rethrow calles std::terminate, and there's the > > infinite loop. > > > > I have no idea why; the core dump I get (and the rest of us got during > > testing) shows this: > > > > #0 0x40124a51 in kill () from /lib/libc.so.6 > > #1 0x40124872 in raise () from /lib/libc.so.6 > > #2 0x40125986 in abort () from /lib/libc.so.6 > > #3 0x400a1fcb in __gnu_cxx::__verbose_terminate_handler() () at > > /home/pme/src/unified/libstdc++-v3/libsupc++/vterminate.cc:96 > > Did you build with --enable-threads? Always. Hmmm... you're on Linux. Can you try building with --enable-__cxa_atexit and see what happens? I've put out a call for help; I'm not familiar with the guts of the _Unwind* framework. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002