From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: libunwind basic support
Date: Wed, 15 Oct 2003 22:40:00 -0000 [thread overview]
Message-ID: <1031015224024.ZM23064@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "RFA: libunwind basic support" (Oct 15, 5:29pm)
On Oct 15, 5:29pm, J. Johnston wrote:
> The attached patch adds basic libunwind frame support. I will be shortly
> submitting an ia64-tdep.c patch which works in conjunction with this patch. The
> libunwind code is protected by looking for the libunwind header files to
> compile. At runtime, the libunwind frame sniffer will fail if either the
> libunwind library cannot be dynamically loaded or the frame in question does not
> have proper libunwind info.
>
> For configuration I have added checks for libunwind.h and libunwind-ia64.h as
> this is being added for ia64 support only at present. Regarding testing, I have
> this code working with my ia64 changes. I have tested on systems with the
> libunwind-0.92 library/headers installed and not installed.
>
> Ok to commit?
>
> 2003-10-15 Jeff Johnston <jjohnstn@redhat.com>
>
> * libunwind-frame.c: New file.
> * libunwind-frame.h: New file.
> * configure.in: Add checks for libunwind.h and libunwind-ia64.h.
> * configure: Regenerated.
> * Makefile.in: Add support for libunwind-frame.o.
> * config.in: Regenerated.
It looks okay to me.
I'm not sure who needs to approve this though -- if it's me, then you
have my approval.
Kevin
next prev parent reply other threads:[~2003-10-15 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 21:29 J. Johnston
2003-10-15 22:40 ` Kevin Buettner [this message]
2003-10-16 20:19 ` Andrew Cagney
2003-10-16 21:38 ` J. Johnston
2003-10-22 23:38 ` J. Johnston
2003-11-11 23:09 ` Andrew Cagney
2003-11-13 23:07 ` J. Johnston
2003-11-14 0:06 ` Andrew Cagney
2003-11-14 21:19 ` J. Johnston
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=1031015224024.ZM23064@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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