On Wed, Nov 11, 2009 at 1:57 AM, fadden <[email protected]> wrote: > On Nov 9, 10:18 pm, Shankar Ganesh <[email protected]> wrote: > > Here, SIGIO is received by signal handler, but my user-space process > (open > > core decoder node process) is hanged and never wakes-up and hence blocked > > within sigsuspend() . > > Can anyone throw some ideas if you have faced similar problem ? > > I don't quite understand -- you say the process receives the SIGIO, > but it's hung and never wakes up. If the process is hung, how do you > know it received the signal? > > Are you sure the signal is being delivered to the correct thread > within the process? > > Thanks for your help. Here signal handler (registered for SIGIO) is called , when SIGIO is raised, but the thread waiting on sigsuspend() never comes-out ( Here sigsuspend should have returned).
> FWIW, the VM uses sigwait() to do something similar. > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
