Re: 'diff != 0' GNU Mach assertion failure

2012-11-20 Thread Richard Braun
On Mon, Nov 19, 2012 at 01:25:54PM +0100, Thomas Schwinge wrote: Richard wants to address this problem, but in the mean time, I'm using the following patch, which makes such a vm_map call return KERN_INVALID_ARGUMENT, translated to EINVAL for mmap (hurd/hurd.h:__hurd_fail). It's actually the

'diff != 0' GNU Mach assertion failure

2012-11-19 Thread Thomas Schwinge
Hi! As discussed on IRC already, the 'diff != 0' GNU Mach assertion failure (vm/vm_map.c:1002), that came in with the recent allocator improvement patch, is as easy as follows to reproduce: vm_map(mach_task_self(), 0, 0, 0, 1, 0, 0, 0, 0, 0, 0); Before that patch, GNU Mach accepted