From: Diego Nieto Cid <dnie...@gmail.com> Hi,
Here is the remaining patches of the VM limit implementation which are those for GLIBC and GNU Mach. I have, however, some trouble running the test case using setrlimit under rpctrace: 27<--40(pid707)->io_write_request ("setrlimit failed: (os/kern) invalid task\n" -1)setrlimit failed: (os/kern) invalid task = 0 41 while running without rpctrace the program completes successfully. The new setrlimit call uses the __mach_task_self () call to get the task port. It's the only hint I have right now and don't knwow how to debug this. It's also inside a HURD_CRITICAL_BEGIN/HURD_CRITICAL_END, could that be a problem? Thanks -- 2.50.0