This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patch: FYI: ignore unknown children when reaping


Tom Tromey wrote:
"Mark" == Mark Wielaard <mark@klomp.org> writes:


+      // Note that if process==NULL, then we have an unknown child.
+      // This is not common, but can happen, and isn't an error.


Mark> So how/when does this happen? And why isn't it an error?

Native code could fork/exec.

If this is the case, there is a potential problem. If whichever entity that forked/execed the process does a wait() then it could reap a process under control of the process manager. In this case the process manager would be screwed.


I would highly recommend figuring out what was causing the message, as it is likely to be incompatible with the way libjcg manages Processes.

Or, as I recall, you can inherit running
children from whatever process exec()d this one.

This should not happen. If your parent is dead, init (pid 1) becomes your parent.

David Daney.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]