From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17453 invoked by alias); 20 Feb 2003 19:36: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 17426 invoked by uid 71); 20 Feb 2003 19:36:01 -0000 Date: Thu, 20 Feb 2003 19:36:00 -0000 Message-ID: <20030220193601.17424.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Stephen M. Webb" Subject: Re: libstdc++/9756: __verbose_terminate_handler enters infinite loop Reply-To: "Stephen M. Webb" X-SW-Source: 2003-02/txt/msg01015.txt.bz2 List-Id: The following reply was made to PR libstdc++/9756; it has been noted by GNATS. From: "Stephen M. Webb" To: Phil Edwards 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