From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11917 invoked by alias); 6 Feb 2003 16:26: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 11892 invoked by uid 71); 6 Feb 2003 16:26:01 -0000 Date: Thu, 06 Feb 2003 16:26:00 -0000 Message-ID: <20030206162601.11891.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Christian Ehrhardt" Subject: Re: c++/9597: Exception crash in shared library on Solaris 2.8 Intel platform Reply-To: "Christian Ehrhardt" X-SW-Source: 2003-02/txt/msg00310.txt.bz2 List-Id: The following reply was made to PR c++/9597; it has been noted by GNATS. From: "Christian Ehrhardt" To: pvantrepote@yahoo.fr Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/9597: Exception crash in shared library on Solaris 2.8 Intel platform Date: Thu, 6 Feb 2003 17:16:57 +0100 On Thu, Feb 06, 2003 at 02:36:54PM -0000, pvantrepote@yahoo.fr wrote: > I got a crash when i throw an exception in a shared library. > I use gcc 3.2.1 on Solaris 2.8 i386 Intel Platform. > [ ... ] Core dumps with shared libs and Solaris rings a bell. However, what I have in mind shouldn't apply to intel targets at all. Could you try the following experiments and tell me if any of these help: - Use the SUN supplied linker to create the shared library - Add -z nocombreloc to the ld flags for the GNU linker - link the shared lib statically into the program. If any of these make a difference send the output of elfdump -G for the shared lib. regards Christian -- THAT'S ALL FOLKS!