From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC/ia64] link against libunwind rather than using dlopen
Date: Tue, 28 Jun 2011 19:55:00 -0000 [thread overview]
Message-ID: <m362np7mv6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110625184854.GA18713@host1.jankratochvil.net> (Jan Kratochvil's message of "Sat, 25 Jun 2011 20:48:54 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> The gdb binary years ago could be freely copied across hosts and it
Jan> still worked.
[...]
Jan> Unfortunately since DT_NEEDED libpython this feature is already lost so it
Jan> should be OK now even for libunwind.so.7.
We could make this work if we truly wanted to. It just seems like a lot
of effort; and building gdb is not so very hard.
The other day I was thinking we could even automate it by reading the
libpython debuginfo to generate weak declarations for the public API :-)
But, ok, that is not practical for regular gdb builds.
Tom
next prev parent reply other threads:[~2011-06-28 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 16:11 Joel Brobecker
2011-06-22 14:40 ` Tom Tromey
2011-06-22 15:36 ` Joel Brobecker
2011-06-25 18:49 ` Jan Kratochvil
2011-06-28 19:55 ` Tom Tromey [this message]
2011-06-29 16:28 ` Joel Brobecker
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=m362np7mv6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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