From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31461 invoked by alias); 29 Jan 2010 17:05:05 -0000 Received: (qmail 29158 invoked by uid 48); 29 Jan 2010 17:04:51 -0000 Date: Fri, 29 Jan 2010 17:05:00 -0000 Message-ID: <20100129170451.29155.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/42679] RTLD_DEEPBIND dlopen option for shared library that uses libstdc++ std::ostream crashes In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mjtruog at fastmail dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-01/txt/msg03333.txt.bz2 ------- Comment #16 from mjtruog at fastmail dot ca 2010-01-29 17:04 ------- I am using "-fpic/-fPIC" and in fact am using: // g++ -g -O0 main.cpp -ldl // g++ -g -O0 -rdynamic -c -fPIC -o library.o library1.cpp // g++ -shared -Wl,-export-dynamic -o library.so library.o I do want to use RTLD_DEEPBIND to keep the libraries in isolation as you mention, since I could have libraries that depend on different versions of GCC. I understand that it doesn't work right now with g++ linking, so I might try to switch to gcc linking. I just was concerned because it appeared to be connected to libstdc++, but I guess it is a g++ linking peculiarity. I don't think ignoring the RTLD_DEEPBIND feature in glibc would help. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42679