On Dec 18, 2014, at 11:51 AM, Corinna Vinschen <corinna-cyg...@cygwin.com> wrote:
> On Dec 18 11:40, Warren Young wrote: >> On Dec 18, 2014, at 10:33 AM, Corinna Vinschen <corinna-cyg...@cygwin.com> >> wrote: >> >>> On Dec 18 10:26, Warren Young wrote: >>>> >>>> ...Cygwin doesn’t do something similar? >>> >>> Cygwin isn't a kernel and the process >>> information is kept in shared memory regions held by the parent process >>> and the process itself. This model has limitations you don't have on a >>> real kernel. >> >> I’m aware of that, but can’t the DLL see both the birth and death of >> every Cygwin process? Birth via either DllMain() or execvp(2), and >> death via one of the methods here: > > Aren't we talking about fetching info from non-Cygwin processes? Of course. But if you keep a table of all Cygwin processes, you can tell whether you’re being asked for info for a native process vs a Cygwin one, and handle <defunct> differently for the two cases. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
