From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: aoss: problems with using functions in dlfcn.h
Date: Fri, 11 Jun 2004 00:56:43 +0100 [thread overview]
Message-ID: <40C8F53B.4010303@superbug.demon.co.uk> (raw)
I have an application (xine) that opens oss output from a plugin.
This plugin is loaded into xine using dlopen(), dlsym() and friends.
When, during runtime, dlsym() resolves the open() function, it bypasses
aoss, and links directly to open() instead of linking to the aoss's
version of open().
Is there any way to fix this problem with dlopen and friends.
Although we don't actually need aoss to work with xine, because xine has
good native alsa support, it just highlights a possible problem that
other apps might have.
James
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next reply other threads:[~2004-06-10 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 23:56 James Courtier-Dutton [this message]
2004-06-11 7:43 ` aoss: problems with using functions in dlfcn.h 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=40C8F53B.4010303@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.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 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.