We recently had a case of a task going into the STOPPED state. My understanding is that this is the result of SIGSTOP. 
We think that the problem was caused by an errant pointer, and it looks like the bug is gone after we fixed the pointer.


What I don't understand is how this problem could have led to the the task being STOPPED. I suppose a random part of RAM
 was being written to, but I don't get how that could have cause d SIGSTOP.

Any comments would be appreciated.