Not sure if this is the proper forum for this question. If not, redirect me. A large process may take a relatively long time to complete dumping core after it catches a signal. Its parent process meanwhile is blissfully unaware of the fact because the sigchld doesnt get delivered until the dumping activity is complete and the child is ready to get reaped.
So the question is, is there a means by which it can be unabiguously the the process of dumping core is now currently ongoing? I've looked at proc(4) and its vague on the topic as far as I can tell. For example, lwpstatus:pr_cursig is described as the "current" signal, but the elaboration says it is the "next" signal to be delivered, as in the future. In the case I'm asking about the signal has already been delivered and the resulting action was to begin dumping core. -d -- This messages posted from opensolaris.org
