Date: Thu, 27 Jul 2000 12:50:22 +0200
From: Marcus Brinkmann <[EMAIL PROTECTED]>
Hi,
I just realized that I am suffering this unexpected error in __fork
problem only in long (several hours) perl runs. The autobuilder is
such a perl program, and it has a lot of system() calls (which is
perlish for fork/exec), which themselve can take a long time.
That's a bit unfortunate, since it's hard too debug if you got to wait
a long time for it to happen.
Does your Hurd crash shortly after it happens, or will it keep
running?
The last time the bug was in the proc server. It was losing point
rights when sending signals to a program. You could use GDB on the
proc server to see if you can spot any cases where the number of port
references is obviously wrong. The `set noninvasive on' and `info
port' commands might be useful.
Mark
