From owner-freebsd-hackers Sun May 11 04:44:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25057 for hackers-outgoing; Sun, 11 May 1997 04:44:58 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25052 for ; Sun, 11 May 1997 04:44:55 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA29259; Sun, 11 May 1997 07:43:15 -0400 (EDT) From: Peter Dufault Message-Id: <199705111143.HAA29259@hda.hda.com> Subject: Re: g++ shared library segfaults (SOLUTION) In-Reply-To: <199705062018.QAA13068@hda.hda.com> from Peter Dufault at "May 6, 97 04:18:49 pm" To: hackers@freebsd.org Date: Sun, 11 May 1997 07:43:14 -0400 (EDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone who uses g++ and shared libraries care to speculate > about this shared library crash in ptolemy? The alpha release of > ptolemy is working fine in a static version, but trying to build > a shared library version is producing this traceback, and I expect > this is a configuration issue on my end. It seems to happen at > the transition from the ptolemy shared library to the g++ shared > library. I'll build a debug version of stdc++ but in the mean time > maybe someone has seen something like this. Now back to the question at hand: David Nugent correctly guessed that I wasn't linking the shared libraries properly and the static constructors weren't executing. Yes - don't overlook the prepending of ${DESTDIR}/usr/lib/c++rt0.o to SOBJS on older systems or the or the use of "gcc -shared" in -current. Thanks, David. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936