From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/ia64] link against libunwind rather than using dlopen
Date: Wed, 22 Jun 2011 14:40:00 -0000 [thread overview]
Message-ID: <m3y60uj5f2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1308327042-6327-1-git-send-email-brobecker@adacore.com> (Joel Brobecker's message of "Fri, 17 Jun 2011 12:10:42 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> This is something that I mentioned back in Aug 2005, and which came back
Joel> to bite me a little. Basically, on ia64 hosts, we dlopen libunwind rather
Joel> that link GDB against it.
[...]
Joel> What do you guys think?
Why do we currently use dlopen?
If there is no good reason, or the reason is obsolete, then it is
definitely better to link against a library than to dlopen it.
Tom
next prev parent reply other threads:[~2011-06-22 14:40 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 [this message]
2011-06-22 15:36 ` Joel Brobecker
2011-06-25 18:49 ` Jan Kratochvil
2011-06-28 19:55 ` Tom Tromey
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=m3y60uj5f2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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