From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <pbd@op.net>
Cc: Juergen Kreileder <jk@blackdown.de>, Tim Goetze <tim@quitte.de>,
Florian Bomers <Florian.Bomers@sun.com>,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: alsalib symbol problem
Date: Tue, 17 Sep 2002 17:17:27 +0200 [thread overview]
Message-ID: <s5h7khksl14.wl@alsa2.suse.de> (raw)
In-Reply-To: <E17rJn4-0006ys-00@usw-sf-list1.sourceforge.net>
At Tue, 17 Sep 2002 10:59:17 -0400,
Paul Davis wrote:
>
> >Paul Davis <pbd@op.net> writes:
> >
> >> the problem is that libasound itself calls dlopen(), and the initial
> >> (non-RTLD_GLOBAL) linkage hasn't put libasound's symbol into the
> >> global namespace. hence, libasound's own dlopen'ed code can't access
> >> libasound itself.
> >
> >I know, that's why I suggested to not do dlopen(NULL, ...) inside
> >libasound (see the code from my previous mail).
>
> how does this help?
it openes /usr/lib/libasound.so.2 (resolved from dladdr) explicitly,
so you'll get symbols from the handle without referring to the global
namespace.
this solution sounds nice to me -- if it really works ;)
can anyone test it?
Takashi
-------------------------------------------------------
Sponsored by: AMD - Your access to the experts on Hammer Technology!
Open Source & Linux Developers, register now for the AMD Developer
Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
next prev parent reply other threads:[~2002-09-17 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17rJDb-0005DN-00@zaphod.blackdown.de>
2002-09-17 14:46 ` alsalib symbol problem Juergen Kreileder
2002-09-17 14:59 ` Paul Davis
2002-09-17 15:17 ` Takashi Iwai [this message]
[not found] <E17rJn3-0005Ec-00@zaphod.blackdown.de>
2002-09-17 15:10 ` Juergen Kreileder
2002-09-17 15:39 ` Florian Bomers
2002-09-17 18:14 ` Tim Goetze
2002-09-17 18:21 ` Florian Bomers
2002-09-17 13:35 Juergen Kreileder
2002-09-17 13:57 ` Paul Davis
2002-09-17 15:32 ` Jaroslav Kysela
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=s5h7khksl14.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Florian.Bomers@sun.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jk@blackdown.de \
--cc=pbd@op.net \
--cc=tim@quitte.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.