On Sat, Jun 22, 2013 at 12:52:03AM +0200, Thomas Schwinge wrote: > But anyway, what is the split-stack run-time/startup code doing so that > it makes vm_allocate behave erratically? Isn't vm_allocate a real system > call after all, but relies on some threadvar state? It's now too late to > figure it out today, and I have enough other things on my plate anyway. > But surely Richard and/or Samuel will have some comments on this? ;-)
Unless I'm mistaken, vm_allocate (along with vm_map and vm_deallocate) is never used through a real system call but always as an RPC from the Hurd. To make sure that's the case, see if rpctrace catches the call. -- Richard Braun
