Date: Tue, 3 Oct 2000 15:58:47 +0200 From: Marcus Brinkmann <[EMAIL PROTECTED]>
On Tue, Oct 03, 2000 at 06:00:52AM -0700, Steve Bowman wrote: > Anything in particular to do to get useful information? Yes. First, find out about the thread and port usage: ps -F hurd-long -x -a Pipe the whole thing into a file for us. Then, "portinfo PID | wc -l" shows the number of open ports, where PID is the pid of pflocal. Then, find out what all those threads do: gdb pflocal ... set noninvasive on attach PID info threads (again, PID being the pid of pflocal) Is some thread stuck in some function? Are many threads stuck in the same function? Good suggestions. But before you do this, you might want to freeze the process by making it crash. `kill -ABRT PID' should do the job provided that the crash server has been set up right. Try `showtrans /servers/crash' to see if it is, and use `settrans /servers/crash /hurd/crash OPTIONS' to set it to do something sensible. I'm not sure what is the default, and you might want to make sure that orphaned processes are suspended. Try `/hurd/crash --help' to see what your options are. Mark
