You need to look at each individual server function and see what is the
right thing for it. There is no generic answer (some things are copying
data they hold elsewhere, some should dealloc). Note there is also
`dealloc[]' to give an argument the server can fill in.
___
On Wed, Jun 27, 2001 at 03:59:03AM +0200, Marcus Brinkmann wrote:
> this is really a nice obscure bug.
Oh man. This is a prime example for what you can read out of data if you
want to.
The real cause of the bug is the allocation of *piarray, which only happens
if the number of threads in the ta
On Wed, Jun 27, 2001 at 03:59:03AM +0200, Marcus Brinkmann wrote:
> To prove that PID 4 is the only process with this
> problem, the below program iterates over all pids. If you specify any command
> line arguments, it will skip PID 4. In this case, no memory is leaked.
#define _GNU_SOURCE
#in
Package: hurd
Version: current
Hi,
this is really a nice obscure bug.
Calling proc_getprocinfo on PID 4 (root filesystem server) causes proc
to leak a couple of kilobytes (pages?) each time. This can easily be
reproduced by
ps -F hurd 0
ps -F hurd 4
ps -F hurd 0
etc. Do this right after boo
