From owner-freebsd-questions@FreeBSD.ORG Mon Dec 31 17:02:00 2007 Return-Path: Delivered-To: FreeBSD-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4855E16A468 for ; Mon, 31 Dec 2007 17:02:00 +0000 (UTC) (envelope-from markus.hoenicka@mhoenicka.de) Received: from rrzmta1.rz.uni-regensburg.de (rrzmta1.rz.uni-regensburg.de [194.94.155.51]) by mx1.freebsd.org (Postfix) with ESMTP id 0B26213C442 for ; Mon, 31 Dec 2007 17:02:00 +0000 (UTC) (envelope-from markus.hoenicka@mhoenicka.de) Received: from rrzmta1.rz.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 61ED550976 for ; Mon, 31 Dec 2007 18:02:04 +0100 (CET) Received: from yeti.mininet (rrzras1-10.rz.uni-regensburg.de [132.199.208.20]) by rrzmta1.rz.uni-regensburg.de (Postfix) with ESMTP id B350D50A2D for ; Mon, 31 Dec 2007 18:02:00 +0100 (CET) X-Mailer: emacs 21.3.1 (via feedmail 8 Q); VM 7.19 under Emacs 21.3.1 From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18296.63950.30082.948425@yeti.mininet> Date: Mon, 31 Dec 2007 15:16:46 +0100 To: FreeBSD-questions@freebsd.org In-Reply-To: <20071231104614.GA1761@kobe.laptop> References: <18295.55864.740395.631672@yeti.mininet> <20071231104614.GA1761@kobe.laptop> Cc: Subject: Re: dlopen(), atexit() on FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Dec 2007 17:02:00 -0000 Giorgos Keramidas writes: > The __cxa_finalize() function is not called by atexit(), but by exit() I see. > Since the program is going to exit and have all its dlopened shared > objects be unmapped, it's probably ok to skip the dlclose() step in > this example. > Just for the record: I've tried disabling the dlclose() call in our code. It both prevents the segfaults and does not seem to inflict any harm. I'll use the code that way for the time being, any real solution for this problem notwithstanding. > I think this is probably something that the freebsd-hackers list will > be interested in. Can you post a description of the problem there too? > I'll do. I haven't read up the full history of this problem, but apparently other programs and libraries are affected too, so it is probably fair to seek assistance. regards, Markus -- Markus Hoenicka markus.hoenicka@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de