From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32589 invoked by alias); 12 Aug 2005 00:04:03 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32521 invoked by uid 22791); 12 Aug 2005 00:03:35 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 12 Aug 2005 00:03:35 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j7C03XOm002382 for ; Thu, 11 Aug 2005 20:03:33 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j7C03SV08905; Thu, 11 Aug 2005 20:03:28 -0400 Received: from localhost.localdomain (vpn50-47.rdu.redhat.com [172.16.50.47]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j7C03NN7024214; Thu, 11 Aug 2005 20:03:23 -0400 Received: from ironwood.lan (ironwood.lan [192.168.64.8]) by localhost.localdomain (8.12.11/8.12.10) with ESMTP id j7C03Ipa004072; Thu, 11 Aug 2005 17:03:18 -0700 Date: Fri, 12 Aug 2005 01:28:00 -0000 From: Kevin Buettner To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] link GDB against libunwind-ia64 Message-ID: <20050811170317.11e4569f@ironwood.lan> In-Reply-To: <20050811222323.GO10325@adacore.com> References: <20050811222323.GO10325@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2005-08/txt/msg00125.txt.bz2 On Thu, 11 Aug 2005 15:23:23 -0700 Joel Brobecker wrote: > I'm currently working on a GDB port for ia64-hpux, and I'm having some > problems with the unwinding of a stacked register. I'm trying to find > the source of the problem, and part of the investigation lead me to look > into the libunwind-ia64 code. > > I noticed that GDB uses the libunwind-ia64 shared library without being > directly linked to it. Instead, it uses dlopen(). > > This method has its advantages, but also introduces an extra layer > of complication that is preventing me from making progress (*): A bug > in my debugger is causing problems when I am attempting operations such > as next or step over code inside that library. > > So I'd like to add an option so that GDB is explicitly linked against > libunwind-ia64, instead of using dlopen(). As a bonus, this may simplify > our work in terms of binary distribution... > > I was wondering if this would be an interesting enhancement to contribute. I'm wondering if there's a good reason to preserve the existing dlopen() mechanism. In other words, why not always link directly against libunwind-ia64? Kevin