public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop Date: Thu, 20 Feb 2003 17:06:00 -0000 [thread overview] Message-ID: <20030220170601.19896.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/9756; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: "Stephen M. Webb" <stephenw@cryptocard.com> 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
next reply other threads:[~2003-02-20 17:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 17:06 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-28 21:06 Stephen M. Webb 2003-02-28 19:11 bkoz 2003-02-20 19:36 Stephen M. Webb 2003-02-20 17:06 Stephen M. Webb 2003-02-20 16:26 Phil Edwards 2003-02-20 16:06 Stephen M. Webb 2003-02-19 22:06 Phil Edwards 2003-02-19 16:06 stephenw
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=20030220170601.19896.qmail@sources.redhat.com \ --to=phil@jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).