From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22314 invoked by alias); 6 Feb 2003 04:56:02 -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 22298 invoked by uid 71); 6 Feb 2003 04:56:01 -0000 Date: Thu, 06 Feb 2003 04:56:00 -0000 Message-ID: <20030206045601.22297.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Alan Modra Subject: Re: c++/9588: memory fault when user throws exception from terminate() Reply-To: Alan Modra X-SW-Source: 2003-02/txt/msg00283.txt.bz2 List-Id: The following reply was made to PR c++/9588; it has been noted by GNATS. From: Alan Modra To: fwang@ca.ibm.com Cc: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/9588: memory fault when user throws exception from terminate() Date: Thu, 6 Feb 2003 15:17:30 +1030 I would guess that you have a library, most likely libc, built with a buggy toolchain that didn't terminate .eh_frame with a zero. You can use a recent (later than 2002-11-04) version of readelf to display the terminator with something like powerpc64-linux-readelf --debug-dump=frames \ /usr/local/powerpc64-linux/lib/libc.so.6 | grep ZERO which should result in xxxxxxxx ZERO terminator As far as I know, Jakub Jelinek fixed the toolchain problem 2002-04-22. -- Alan Modra IBM OzLabs - Linux Technology Centre