libaoss.so hole?

["Joe Hsu" <nagual.hsu@gmail.com>]

    I've tested over and over. With my limited number of computers,
I've found this problem only happens in the computers with intel8x0
audio chips:

    I have an oss application which registers SIGCHLD signal handler
in the beginning and then opens /dev/dsp, and then forks a child
process. If the child process dies, the father process would receive a
SIGCHLD process and then free the allocated resources and then exit.

    Without pre-loading libaoss.so, everything goes well. With
libaoss.so pre-loaded, my applications exit in the computers with
intel8x0 audio chips because my application receives SIGCHLD signal
and thinks its process were dead. But in fact, it does not fork the
child process yet.

    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.

    However, other computers with other audio chips go through the
same process (/dev/dsp0 failed and then alsa-default  device
successfully), but my application does not receive any un-expected
SIGCHLD signal before forking its own child process.

    I guess this is a hole. Any body thinks so ?


--
The sun is shinny but the ice is slippery.


-------------------------------------------------------
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\x110944&bid$1720&dat\x121642