From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30142 invoked by alias); 22 Jun 2011 15:36:52 -0000 Received: (qmail 30100 invoked by uid 22791); 22 Jun 2011 15:36:51 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Jun 2011 15:36:33 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 732D32BAC3D; Wed, 22 Jun 2011 11:36:32 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DoS+iQ0XRNFF; Wed, 22 Jun 2011 11:36:32 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 480D12BABF7; Wed, 22 Jun 2011 11:36:32 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 3E786145615; Wed, 22 Jun 2011 08:36:25 -0700 (PDT) Date: Wed, 22 Jun 2011 15:36:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: [RFC/ia64] link against libunwind rather than using dlopen Message-ID: <20110622153625.GA20676@adacore.com> References: <1308327042-6327-1-git-send-email-brobecker@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00307.txt.bz2 > Joel> This is something that I mentioned back in Aug 2005, and which came back > Joel> to bite me a little. Basically, on ia64 hosts, we dlopen libunwind rather > Joel> that link GDB against it. > [...] > Joel> What do you guys think? > > Why do we currently use dlopen? Hard to answer that question for certain. I had a hunch shortly after I sent this message, though: On the (relatively old) Linux machine that we have at AdaCore, I can't link against the system libunwind. I think it's a linker bug, as the linker is complaining about missing symbols, whereas I can see them fine. These are protected symbols, but they are there. No problem with GNU libunwind. But I did send a message to Jan asking him if he could test on a newer distro, and he said that he'd get back to me as soon as he has time. -- Joel