From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15227 invoked by alias); 27 Aug 2002 20:58:05 -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 15220 invoked from network); 27 Aug 2002 20:58:04 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 27 Aug 2002 20:58:04 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA24740; Tue, 27 Aug 2002 13:50:57 -0700 (PDT) Message-ID: <3D6BE7DB.DEE78AE0@redhat.com> Date: Tue, 27 Aug 2002 14:00:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: davidm@hpl.hp.com CC: gdb-patches@sources.redhat.com, ac131313@ges.redhat.com, kevinb@redhat.com Subject: Re: [patch] unwind support for gdb/ia64 References: <200207102315.g6ANFMHh022230@napali.hpl.hp.com> <3D6AE2ED.53D9E877@redhat.com> <15722.62020.64894.433304@napali.hpl.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00910.txt.bz2 David Mosberger wrote: > > Michael> David Mosberger wrote: > >> I'd like to submit the attached patch for inclusion in the gdb > >> source tree. It adds support for determining the frame chain > >> based on unwind information (which is supplied by the libunwind > >> library). The patch is relative to today's CVS tree (July 10th) > >> and should be safe for all platforms: > >> > >> - it adds only one new function to blockframe.c > >> (generic_dummy_frame_chain()) - it adds one new file > >> (unwind-common.h) - all other non-trivial changes are contained > >> in ia64-tdep.c; even for the ia64 case, the patch has no effect > >> _unless_ the libunwind header file and library are installed on > >> the build machine > >> > >> For the sake of completeness, I'd like to point out that > >> libunwind is built in a fashion that support gdb-style > >> multi-arch'ing, so there are no issues in building a cross-gdb or > >> a gdb that supports multiple targets that use libunwind (though > >> at the moment, there is only an ia64 version of libunwind; > >> hopefully that will change over time). > >> > >> Thanks, > >> > >> --david > > Michael> I don't see any replies to this patch. > > Ditto here. > > Michael> Has it been resolved? > > No, unfortunately. > > I'd really like to see libunwind support in gcc, so I'd welcome any > help in making this happen. Well, I can't review the ia64 parts, but the rest of it is fine.