All of lore.kernel.org
 help / color / mirror / Atom feed
From: nagual.hsu <nagual.hsu@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: libaoss.so hole?
Date: Mon, 20 Mar 2006 02:18:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060320T031107-48@post.gmane.org> (raw)
In-Reply-To: s5h4q1xt3oe.wl%tiwai@suse.de

Takashi Iwai <tiwai <at> suse.de> writes:

> 
> >     After I turn on the ALSA_OSS_DEBUG environment variable,
> > libaoss.so first tried to open /dev/dsp0 but in vain. Then it tried a
> > alsa-default device successfully. I can see that every time libaoss.so
> > tries to opena pcm device with a new thread. And thta's the source of
> > the un-expected SIGCHLD signal.
> 
> No, aoss has no single code calling any thread functions...
> 
> Takashi
> 

    Maybe, it's the dmix and it is turned on as default since version
 1.0.10. I tried this with version 1.0.10.

    Check the following code run on computers with intel8x0 chips 
pre-loading libaoss.so:

#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <signal.h>

void handler(int signum)
{
	fprintf(stderr, "signal...%d == SIGCHLD??\n", signum);
	return;
}

int main(int argc, char *argv[])
{
	int fd;
	signal(SIGCHLD, handler);
	signal(SIGTERM, handler);
	
	fd = open("/dev/dsp", O_WRONLY);
	fprintf(stderr, "success...\n");
	close(fd);
	return 0;
}






-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-03-20  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 13:12 libaoss.so hole? Joe Hsu
2006-03-17 16:51 ` Takashi Iwai
2006-03-20  2:18   ` nagual.hsu [this message]
2006-03-17 17:49 ` Dirk Jagdmann
2006-03-17 23:20   ` Joe Hsu
2006-03-17 23:27     ` Joe Hsu
2006-03-20 11:46       ` Takashi Iwai

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=loom.20060320T031107-48@post.gmane.org \
    --to=nagual.hsu@gmail.com \
    --cc=alsa-devel@lists.sourceforge.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.