Re: libaoss.so hole?

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

2006/3/18, Dirk Jagdmann <doj@cubic.org>:
> >     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.
>
> I don't see any problem here if you did your code right.
> 1) fork() does return the pid of the child
> 2) in your SIGCHLD handler call wait(int*) which returns the pid of the
> terminated process.
> 3) If the pid from fork() and wait() match you can do your cleanup()
> 4) If they don't match, simply ignore the signal, as some other process
> (probably from the alsa lib) has died.
>
> --
> ---> Dirk Jagdmann ^ doj / cubic
> ----> http://cubic.org/~doj
> -----> http://llg.cubic.org
>
    Of course. I know what you mean. But that is like a work around to
me. And I did a work around too. Since many oss developers didn't
think about the oss-to-alsa layer, this layer must be as transparent
as possible.
    Well, just my own opinion.
--
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