All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Florian Schmidt <mista.tapas@gmx.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Possible solution for the alsa-oss fopen problem.
Date: Thu, 10 Jun 2004 13:49:07 +0100	[thread overview]
Message-ID: <40C858C3.1030401@superbug.demon.co.uk> (raw)
In-Reply-To: <20040610140943.2d11d904@mango.fruits.de>

Florian Schmidt wrote:
> On Wed, 09 Jun 2004 12:10:45 +0100
> James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
> 
> 
>>I have found out that the artsdsp /dev/oss redirector supports fopen and 
>>friends.
>>I looked at the artsdsp, (find it inside arts-1.2.2.tar.bz2)
>>It uses a function called fopencookie()
>>
>>Extract from /arts-1.2.2/artsc/stdioemu.c below.
>>
>>Would this be useable in the alsa-oss redirector?
> 
> 
> This fopencookie seems to be a libc thing to implement custom streams.. See
> 
> http://wwwwbs.cs.tu-berlin.de/user-taipan/kraxel/gnuinfo/libc/Streams_and_Cookies.html
> 
> Might be exctly the thing which is needed to intercept fopen() and friends AND handle the intercepted calls gracefully..
> 
> I have a question though: If this works for alsa-oss, then the libc problem with the internal symbols of open() and friends is solved. But i wonder if there are any other libs which are as "evil" in this regard as libc is. The basic problem persists: If a lib uses internal symbols for open() and friends and an app uses that lib to access /dev/dsp, etc., then we're screwed again..
> 
> On the other hand: How many libs besides libc do stuff like this? And how many apps use such a lib? I would guess: very very few.. If this is the case, i suppose it will work well (tm)
> 
> Florian Schmidt
> 

Does anyone have a small test app that uses fopen and friends, so that I 
could test them if I add fopencookie() to aoss.

Hopefully, the test app should use the fopen and friends calls in the 
same way that know "problem" apps use.

If there is not a test app out there, can someone please tell me more 
details about the problem, so that I could build a test app myself.

I need to know which fcalls lead to a failure, so that if I get those 
fcalls working, these "problem" apps will be guaranteed to work.

Cheers
James



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org

      reply	other threads:[~2004-06-10 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 11:10 Possible solution for the alsa-oss fopen problem James Courtier-Dutton
2004-06-09 11:33 ` Jaroslav Kysela
2004-06-09 11:56   ` James Courtier-Dutton
2004-06-10 12:09 ` Florian Schmidt
2004-06-10 12:49   ` James Courtier-Dutton [this message]

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=40C858C3.1030401@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mista.tapas@gmx.net \
    /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.