Clarification:  an abnormal condition where the kernel sends a SIGKILL, such as high interrupt load or not clearing the 
interrupt condition to prevent the "out of interrupt events".

The kernel does try to do some detection of which interrupt source is causing the "Out of Interrupt Events" and will 
attempt to SIGKILL that process.

If you add several (at least 2) -v's to your procnto in your buildfile then you will see additional debug information 
come out on the debug port.

However debugging an resmgr with an ISR is likely to cause this scenario because the process is not receiving the events
 the interrupt is trying to deliver.

Michael Li wrote:
> Hello,
> 
> Is there a case in QNX 6.4.0 where the kernel would send a SIGKILL to a process?  I'm debugging a resmgr ISR and gdb 
is reporting that the resmgr received SIGKILL.
> 
> Thanks,
> Mike
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post17112
> 

-- 
cburgess@qnx.com