Da Zheng, le Wed 17 Mar 2010 20:00:11 +0800, a écrit : > On 10-3-17 下午6:31, Samuel Thibault wrote: > >> After I get pid from ps, how do I map it to task ID in kdb? > > > > You can't, only the proc server knows that. But for the initial tasks, > > you know in which order they get started, and thus their task number. > so in many cases (the warning is triggered by ordinary programs), kdb cannot > help us find the process that triggers the warning as task ID cannot tell us > much information
Yes, that's unfortunate that the very design of the Hurd makes it hard: exec knows the binary name, proc knows the pid. Nobody knows it all. A solution could be to have gnumach find out in the proc memory space where the task/pid association is. Or you modify the proc server to dump the task/pid association on each process spawn. > and the command column is usually empty. Mmm, the command column is normally only empty if the page got swapped out. If you disable the swap completely, there shouldn't be a problem. Samuel
