Srikanth, The use of a signal (SIGUSR1) by the codecs was removed in the later releases of the codecs. This should fix the issues you are seeing and make it easier to debug using gdb. You can find how to upgrade at http://davincidsp.com and registering your board.
Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Srikanth Nori Sent: Tuesday, November 04, 2008 8:51 PM To: [email protected] Subject: nanosleep failing with EINTR during video process calls on DM355 Hey all, I have observed on DM355 that if one thread tries to "sleep" while another thread is making video encode/decode process calls the sleep fails. I see the same behaviour even in the encodedecode demo that came with the DVSDK. I used the nanosleep API to sleep for 2s in one thread while the video encode/decode was running and the nanosleep failed with an EINTR error (immediately). The perror print is (unsurprisingly :-) ) "Interrupted system call". Any ideas why this could be happening? One thing I did notice is that the process calls on 355 seem to be generating SIGUSR1 interrupts on DM355. You can see this if you run the encodedecode demo usingg gdb. Could it be because of this? If so, any idea how I can prevent this interrupt from interrupting the nanosleep? --- Srikanth Nori _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
