From: Andrew Cagney <cagney@gnu.org>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Patch to handle new libunwind release
Date: Wed, 04 Aug 2004 18:17:00 -0000 [thread overview]
Message-ID: <4111283B.9000902@gnu.org> (raw)
In-Reply-To: <410FB16F.80107@redhat.com>
> The attached patch changes libunwind-frame.c to dlopen "libunwind-xxxx.so" instead of "libunwind.so". This is needed as the design has changed in libunwind 0.97 and the interface functions are no longer found in the vanilla library. Without the patch, ia64 debugging will revert to the examine prologue method which cannot handle a number of scenarios, including backtraces on threads.
>
> Tested on ia64 with libunwind-0.96 and libunwind-0.97.
>
> Ok to commit?
>
> 2004-07-28 Jeff Johnston <jjohnstn@redhat.com>
>
> * libunwind-frame.c (LIBUNWIND_SO): Change to be of form:
> libunwind-xxxx.so" where xxxx is UNW_TARGET.
>
I feel ill
+#ifndef LIBUNWIND_SO
+#define LIBUNWIND_SO "libunwind-" STRINGIFY(UNW_TARGET) ".so"
+#endif
however, we've clearly got no choice, so "obvious".
Andrew
next prev parent reply other threads:[~2004-08-04 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 15:38 Jeff Johnston
2004-08-04 18:17 ` Andrew Cagney [this message]
2004-08-06 18:44 ` Jeff 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=4111283B.9000902@gnu.org \
--to=cagney@gnu.org \
--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