public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Stephen M. Webb" <stephenw@cryptocard.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 19:36:00 -0000	[thread overview]
Message-ID: <20030220193601.17424.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9756; it has been noted by GNATS.

From: "Stephen M. Webb" <stephenw@cryptocard.com>
To: Phil Edwards <phil@jaj.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop
Date: Thu, 20 Feb 2003 14:32:01 -0500

 On February 20, 2003 12:03 pm, Phil Edwards wrote:
 >
 > I've put out a call for help; I'm not familiar with the guts of the
 > _Unwind* framework.
 
 I found my problem.
 
 I seems that the library libgcc_s.so.1 has been changed between 3.2 and the 
 latest CVS source, but does not have versioning support.  Because of the 
 twisty maze of little passages used to resolve dynamic linker dependencies my 
 programs built with the 3.4 compiler were picking up the incompatible 3.2 
 libgcc_s.so.1.
 
 I guess 9756 should be closed.  Someone might consider bumping the version 
 number on that library, though, if version incompatibilities are going to 
 cause runtime errors.
 
 -- 
 Stephen M. Webb
 


             reply	other threads:[~2003-02-20 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 19:36 Stephen M. Webb [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 17:06 Stephen M. Webb
2003-02-20 17:06 Phil Edwards
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=20030220193601.17424.qmail@sources.redhat.com \
    --to=stephenw@cryptocard.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: link
Be 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).