Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: davidm@hpl.hp.com, gdb-patches@sources.redhat.com,
	ac131313@ges.redhat.com, kevinb@redhat.com
Subject: Re: [patch] unwind support for gdb/ia64
Date: Tue, 27 Aug 2002 06:35:00 -0000	[thread overview]
Message-ID: <15722.62020.64894.433304@napali.hpl.hp.com> (raw)
In-Reply-To: <3D6AE2ED.53D9E877@redhat.com>


  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.

	--david


  reply	other threads:[~2002-08-27  3:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 17:54 David Mosberger
2002-08-26 20:12 ` Michael Snyder
2002-08-27  6:35   ` David Mosberger [this message]
2002-08-27 14:00     ` Michael Snyder
2002-08-27 16:28       ` David Mosberger
2002-08-27 16:56         ` Andrew Cagney
2002-08-27 18:24           ` David Mosberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15722.62020.64894.433304@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=ac131313@ges.redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=msnyder@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox