On Jan 29, 1:25 am, "kd.itbhu" <[email protected]> wrote: > I am using SIGUSR1 with timer. After timeout Signal is emitted and it > stops the execution. But call back associated with it, is not called.
If you're running this inside a Dalvik VM process, you're going to be fighting with the SignalCatcher thread, which does a sigwait() to catch SIGQUIT and SIGUSR1. (SIGQUIT causes a stack dump to be written to the log file, SIGUSR1 causes a heap dump to be written to /data/ misc.) The man page for sigwait says, "If the delivered signal has a signal handler function attached, that function is not called." As with other VMs, you can specify "-Xrs" to prevent catching of these signals. If you're doing this as part of an Android app, you have no control over how the VM is started, and will have to use a different signal (perhaps SIGUSR2). --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
