From owner-freebsd-hackers Fri May 9 10:02:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15934 for hackers-outgoing; Fri, 9 May 1997 10:02:35 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15928 for ; Fri, 9 May 1997 10:02:33 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id KAA29357; Fri, 9 May 1997 10:02:24 -0700 (PDT) Message-Id: <199705091702.KAA29357@austin.polstra.com> To: dufault@hda.com Subject: Re: g++ shared library segfaults Newsgroups: polstra.freebsd.hackers In-Reply-To: <199705062018.QAA13068@hda.hda.com> References: <199705062018.QAA13068@hda.hda.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 09 May 1997 10:02:24 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199705062018.QAA13068@hda.hda.com>, Peter Dufault wrote: > Does anyone who uses g++ and shared libraries care to speculate > about this shared library crash in ptolemy? Does it use exceptions? Exceptions + PIC don't work right on any i386 platform. There is register corruption. I'm not sure whether an exception even has to be taken in order for the problem to appear. I contacted Mike Stump about it some time ago, and said, "I don't see a simple way to fix this, do you?" He said, "That's right. Wait for 2.8". -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth